Predictive resource scheduling for efficient sales and marketing acceleration

ABSTRACT

A system and method for establishing a communication with a customer by an agent, via one or more communication modes includes an agent computer and a second computer. The agent computer receives an identify notification that enables the agent computer to identify a customer for the communication, and receives agent schedule information that enables identifying a schedule timeslot of the agent as predicted by the system for a communication session. The second computer provides the identify notification enabling the agent computer to identify the identified customer. The system predicts the schedule timeslot of the agent, by taking into account a number of agent based touches that may need to be executed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending application Ser. No.14/809,213, filed Jul. 25, 2015 and entitled COMPREHENSIVE SYSTEM ANDMETHOD FOR PROVIDING SALES AND MARKETING ACCELERATION AND EFFECTIVENESS.Application Ser. No. 14/809,213 claims the benefit of U.S. ProvisionalPatent Application Ser. No. 62/029,154, filed Jul. 25, 2014, entitled“COMPREHENSIVE SYSTEM AND METHOD FOR PROVIDING SALES AND MARKETINGACCELERATION AND EFFECTIVENESS,” both of which are incorporated byreference herein in their entirety. Application Ser. No. 14/809,213 isalso a continuation-in-part of patent application Ser. No. 14/565,948entitled “SYSTEM AND METHOD FOR PROVIDING SALES AND MARKETINGACCELERATION AND EFFECTIVENESS,” filed Dec. 10, 2014, (issued as U.S.Pat. No. 9,237,233), which is a continuation of U.S. patent applicationSer. No. 14/204,505 entitled “SYSTEM AND METHOD FOR PROVIDING SALES ANDMARKETING ACCELERATION AND EFFECTIVENESS,” filed on Mar. 11, 2014(issued as U.S. Pat. No. 8,938,058), which claims the benefit of U.S.Provisional Patent Application Ser. No. 61/776,351, entitled “SYSTEM ANDMETHOD FOR SALES AND MARKETING DIAGNOSIS AND EFFECTIVENESS,” filed Mar.11, 2013, and which is a continuation-in-part of patent application Ser.No. 14/057,758, entitled “SYSTEM AND METHOD FOR MAXIMIZING EFFICIENCY OFCALL TRANSFER SPEED,” filed Oct. 18, 2013 (issued as U.S. Pat. No.8,964,963), which is a continuation of U.S. patent application Ser. No.13/278,764, entitled “SYSTEM AND METHOD FOR MAXIMIZING EFFICIENCY OFCALL TRANSFER SPEED,” filed Oct. 21, 2011, (issued as U.S. Pat. No.8,594,308) which claims the benefit of U.S. Provisional Application No.61/405,587, entitled “SYSTEM AND METHOD FOR MAXIMIZING EFFICIENT CALLTRANSFER SPEED,” filed Oct. 21, 2010, each of which is herebyincorporated by reference in its entirety. It should be noted that aterm that is not defined in this document may be defined in the U.S.patent application Ser. No. 14/204,505.

FIELD OF THE INVENTION

The present invention is generally related to call centers, sales andmarketing, and more particularly, is related to efficient handling ofcommunication with leads and customers.

BACKGROUND OF THE INVENTION

The prior systems and methods may not provide information associatedwith a customer to a texting rep prior to transferring a text-basedconnectivity from being between a texting agent and the customer tobeing between the texting rep and the customer. However, to allow thetexting rep to be prepared in anticipation of the transfer of the textbased connectivity with the customer, it is beneficial for the textingrep to access information regarding the customer before such transfer.

The prior systems and methods do not provide an effective solution to:optimize contact plans, plan for an agent's availability, and plan for asystem resource's availability based on agent availability data, systemresource availability data, and volume of leads to be contacted.Further, a lead may require more than one follow up/touch and such morethan one touch may not be effectively planned or executed by a contactplan taught by the prior art.

Further, it is desirable to have a system and method that enablescompliance to the Telephone Consumer Protection Act (TCPA) rules, and/orautomates the tracking of behavior of a user and taking correctiveaction if necessary. Accuracy of various computer learning methods mayneed to be evaluated on an on-going basis with new training data set(s),as they become available, to select the optimal computer learning methodthat may yield optimal prediction. Hence, it is desirable to have asystem and method to keep track of how each computer learning method isperforming as new training data sets become available and select anoptimal computer learning method that may yield optimal prediction.

It is desirable to have a system and method that overcomes one or moreof the foregoing limitations. More than one unfulfilled needs andassociated shortcomings of the prior art are introduced in relevantcontexts under the detailed description. Therefore, there is a need inthe industry to address one or more of the abovementioned shortcomings.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide predictive resourcescheduling for efficient sales and marketing acceleration. Brieflydescribed, the present invention is directed to a system and method forestablishing a communication with a customer by an agent, via one ormore communication modes. The system includes an agent computer thatreceives an identify notification that enables the agent computer toidentify a customer for the communication, and receives agent scheduleinformation that enables identifying a schedule timeslot of the agent aspredicted by the system for a communication session. A second computerprovides the identify notification enabling the agent computer toidentify the identified customer. The system predicts the scheduletimeslot of the agent, by taking into account a number of agent basedtouches that may need to be executed.

Other systems, methods and features of the present invention will be orbecome apparent to one having ordinary skill in the art upon examiningthe following drawings and detailed description. It is intended that allsuch additional systems, methods, and features be included in thisdescription, be within the scope of the present invention and protectedby the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a furtherunderstanding of the invention, and are incorporated in and constitute apart of this specification. The components in the drawings are notnecessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the present invention. The drawingsillustrate embodiments of the invention and, together with thedescription, serve to explain the principals of the invention.

It should be noted that any process descriptions or blocks in flowchartsshould be understood as representing modules, segments, portions ofcode, or steps that include one or more instructions for implementingspecific logical functions in the process, and alternativeimplementations are included within the scope of the present inventionin which functions may be executed out of order from that shown ordiscussed, including substantially concurrently or in reverse order,depending on the functionality involved, as would be understood by thosereasonably skilled in the art of the present invention. In addition, itmay be the case that a function may be skipped.

FIG. 1 is a schematic diagram illustrating a system wherein phone callbased communication and text based communication are allowed, that is avariation of the system illustrated in FIG. 1 disclosed in the U.S.patent application Ser. No. 13/278,764.

FIG. 2 is a schematic diagram illustrating an example of a system forexecuting functionality of the present invention.

FIG. 3 is an exemplary screen view illustrating an interface provided toa texting rep, for distinguishing two customers in a first manner aftertheir text based connectivity meets Potential Transfer Criteria, and atransferred customer distinguished in a second manner after the textbased connectivity with the customer met the Connection TransferCriteria, in accordance with the system of FIG. 1.

FIG. 4 is an exemplary screen view illustrating an interface provided toa texting agent, wherein two customers that met Potential TransferCriteria are distinguished in a first manner, and a customer that metConnection Transfer Criteria is distinguished in a second manner, inaccordance with the system of FIG. 1.

FIG. 5 is a flowchart illustrating actions performed when a textingagent computer receives one or more customer records and initiatesconnection attempts via text message, in accordance with the system ofFIG. 1.

FIG. 6 is a flowchart illustrating actions performed by a texting agentwhen a text based connection with a customer meets Connection TransferCriteria, in accordance with the system of FIG. 1.

FIG. 7 is a flowchart illustrating actions performed when a lead isassigned to a multi-touch marketing campaign (MTMC), in accordance withan embodiment of a Digital Communication Assistant (DCA).

FIG. 8 is a flowchart illustrating actions performed when atouch/connection attempt or a MTMC getting updated proactively based onagent availability, in accordance with an embodiment of a DCA.

FIG. 9 is a flowchart illustrating actions performed when atouch/connection attempt is executed, in accordance with an embodimentof a DCA.

FIG. 10 is an exemplary screen view illustrating an interface showingthe required agent availability to execute agent based touches (foroptimal performance) versus the actual agent availability, for varioustimeslots, using a combination of bar and line graph, in accordance withan embodiment of a DCA.

FIG. 11 is an exemplary screen view illustrating an interface to specifycriteria associated with lead characteristics to assign a lead to aMTMC, in accordance with an embodiment of a DCA.

FIG. 12 is an exemplary screen view illustrating an interface of atalker communicating with leads using phone call based communication,wherein dialing agent functionality is fully automated, wherein theleads are selected for phone call based communication based ontalker/agent availability, in accordance with an embodiment of a DCA.

FIG. 13 is an exemplary screen view an interface of a texting repcommunicating with leads using text based communication, wherein textingagent functionality is fully automated, wherein the leads are selectedfor text based communication based on texting agent/agent availability,in accordance with an embodiment of a DCA.

FIG. 14 is an exemplary screen view illustrating an interface thatallows a user to assign weightage for data groups, in accordance with anembodiment of the system 70 (FIG. 1) that generates sale predictionscore.

FIG. 15 is an exemplary screen view illustrating an interface thatallows a user to enable Telephone Consumer Protection Act (TCPA)compliance feature, in accordance with an embodiment of TCPA compliancemodule.

FIG. 16 is a flowchart illustrating actions performed when processing agiven customer name and a given phone number associated with thecustomer name to validate whether the phone number is a mobile phonenumber and if it is a mobile phone number whether consent is receivedfrom the current owner of the phone number, in accordance with anembodiment of TCPA compliance module.

FIG. 17 is a flowchart illustrating actions performed when a customerrecord is selected for connection attempt, in accordance with anembodiment of system 70 (FIG. 1) that processes new customer records.

FIG. 18 is an exemplary screen view illustrating an interface showingnew customer records, in accordance with an embodiment of system 70(FIG. 1) that processes new customer records.

FIG. 19 is a flowchart illustrating actions performed to fetch screenpop information and deliver screen pop information to an agent computerwhen a new incoming call arrives to a queue, in accordance an embodimentof the system 70 (FIG. 1) that processes incoming phone calls and havequeue visibility functionality.

FIG. 20 is a flowchart illustrating actions performed when transferringa an incoming call waiting in the queue, to an available agent thatanswers the incoming call, in accordance with an embodiment of system 70(FIG. 1) that processes incoming phone calls and have queue visibilityfunctionality.

FIG. 21 is an exemplary screen view illustrating an interface showingcustomer records associated with incoming calls waiting in one or morequeues, in accordance with an embodiment of system 70 (FIG. 1) thatprocesses incoming calls and have queue visibility functionality.

FIG. 22 is a flowchart illustrating actions performed when connectdisposition field is updated, in accordance with an embodiment ofWorkflow Module.

FIG. 23 is an exemplary screen view illustrating an interface showing alist of workflow rules configured, in accordance with an embodiment ofWorkflow Module.

FIG. 24 is a flowchart illustrating actions performed by a Purchaserduring a purchase, in accordance with an embodiment of the EcommerceFunctionality.

FIG. 25 is an exemplary screen view illustrating an interface showing afirst step when a Purchaser purchases a Product, in accordance with anembodiment of the Ecommerce Functionality.

FIG. 26 is an exemplary screen view illustrating an interface showing asecond step when a Purchaser purchases a Product, in accordance with anembodiment of the Ecommerce Functionality.

FIG. 27 is an exemplary screen view illustrating an interface showing athird step when a Purchaser purchases a Product, in accordance with anembodiment of the Ecommerce Functionality.

FIG. 28 is a flowchart illustrating actions performed to track andmonitor a user behavior, in accordance with an embodiment of BehaviorTracking and Learning Management System (BTLMS).

FIG. 29 is an exemplary screen view illustrating an interface showing afirst step in defining a Pre-defined Pattern and associated trainingcourse(s), in accordance with an embodiment of BTLMS.

FIG. 30 is an exemplary screen view showing a second step in defining aPre-defined Pattern and associated training course(s), in accordancewith an embodiment of BTLMS.

DETAILED DESCRIPTION

One having ordinary skill in the art would understand and appreciatethat the concepts, methods, and systems described in the U.S. patentapplication Ser. No. 13/278,764, U.S. patent application Ser. No.14/204,505, and this document are applicable to many different fields,including but not limited to, call center, sales, recruiting,telemarketing, customer relationship management (CRM), phone surveys,census information gathering, political campaigns, fund raising, and thelike. Though the many embodiments and variety of examples are providedherein referencing sales process/selling/sales reps, the system andmethod described in this document may be applicable to other situationssuch as customer support, recruiting, business to businesscommunication, business to consumer communication, and the like, andaccordingly the application of the system and method should not belimited to sales process/selling/sales reps.

One having ordinary skill in the art would understand and appreciatethat based on implementation preferences, in the Dialing Agent Module(defined in the U.S. patent application Ser. No. 14/204,505) the orderof phone connectivity established with the customer and talker may bereversed or performed concurrently. That is, the Dialing Agent Modulemay establish a phone connectivity with the talker and then proceed todial the phone number of the customer (and bridge such customer phonecall with the phone connectivity with the talker), or dial the phonenumber of the customer and then establish phone connectivity with thetalker (and bridge the talker phone connectivity with the customer phonecall), or concurrently dial the phone number of the customer andestablish phone connectivity with the talker (and bridge the customerphone call with the phone connectivity with the talker).

While much of the description in this specification generally refers tovoice communication, embodiments of the present invention are notlimited to voice communications.

While the following describes the present system and method in detail itis beneficial to provide certain definitions.

Based on the context, the word “user” refers to a talker, dialing agent,texting rep, texting agent, Call Handler (disclosed in the U.S. patentapplication Ser. No. 14/204,505), Third Party Call Participant(disclosed in the U.S. patent application Ser. No. 14/204,505) oranother user of the System 70 (FIG. 1). For easier writing andunderstanding, the description may refer to a singular actor or modulein the system, as in “a talker,” “a dialing agent,” “a texting rep,” “atexting agent,” or “a user.” However, one having ordinary skill in theart would appreciate that based on the context such reference may not belimited to singular actor/module and instead it may refer to pluralityof actors/modules. It should be noted that the word “actor” refers to aperson acting in a role and performing the function(s) associated withthe role in the system.

Based on the context, a reference to the term “customer” may mean toinclude “lead” also.

The term “dialing agent” refers to a person who is the first person thathandles a call made to a customer and navigates the call (through phonevoice menus, phone operators, voicemails, wrong phone numbers, and thelike) until the call reaches the correct target customer on the customerlist, while the system may dial the telephone number of the customer andestablishes connection between the person's phone and customer in thecustomer list, where the person transfers a live customer call to atalker, via a central communication server.

The term “talker” refers to a person who accepts a transferred telephonecall and speaks to a customer after the transfer of the telephone call.

The term “texting agent” refers to a person who is the first person thathandles a text based connectivity with a customer and after certaincriteria is met, transfers the connectivity from being between theperson and the customer to being between a texting rep and the customer.

The term “texting rep” refers to a person who accepts a transferred textbased connectivity with a customer and proceeds to communicate via textwith the customer.

The term “connect” refers to connection established between a personusing a system (referenced in the context) and a customer, using acommunication mode (referenced in the context). For example, in thecontext of phone call based communication, the term connect refers to atelephone call established between a person using the system and a livecustomer; in the context of text based communication, the term “connect”refers to a text message based connectivity wherein the customer and atexting agent (or a texting rep) are engaged in communication via textmessage communication or responding to each other's one or more textmessages in a reasonable response time customary in text message basedcommunication (such response time may be customized to qualify as areasonable response time), which may or may not be in real time.

The term “agent” refers to a person involved in communication (via oneor more phone call based or non-phone call based communication modes)with a customer or lead. For example, the term “agent” may refer to atalker, dialing agent, texting rep, texting agent, Call Handler, ThirdParty Call Participant, or another user of a system, based on thecontext. An agent or a user in the system may act in a role or act asanother user and perform the function(s) associated with therole/another user in the system. If a function of a user is automated inthe system, the user may not be a person and instead the function of theuser may be automated, for example, in the case of a user acting as anagent, such agent may not be a person and instead the agent may beautomated (for example, by a computerized voice/menu system, textingsystem, or the like).

The term “agent computer” refers to a computer used by the agent.

The term “agent data” refers to one or more attributes/characteristicsassociated with an agent, including but not limited to personalcharacteristics. Based on the context, the term “agent data” may referto such data associated with plurality of agents.

The term “agent availability data” refers to one or moreattributes/characteristics associated with time availability of an agent(to perform a function referenced in the context). Based on the context,the term “agent availability data” may refer the said data associatedwith plurality of agents.

The term “lead” refers to a prospect, customer, past customer, contactperson, contact person enquiring about certain information, contactperson with a potential opportunity, and the like, based on the context.

The term “lead data” refers to one or more records (each such record isreferred to herein as the “lead record”) associated with a lead, whereineach such lead record may have one or more attributes. For example, alead data may be comprised of one or more attributes including but isnot limited to, name, physical address, one or more phone numbers(landline, mobile phone, and the like), do-not-call, do not call until,fax number, email address, email opt out, instant messaging address, oneor more social media handles/addresses, business name, title, interest,available timings, preferred communication mode(s), preferred time(s)for contacting via one or more communication modes, informationsubmitted by the person associated with the lead via web form or othermethods, and the like. Minimum amount of data associated with a leadthat allows a user to communicate with the lead via one or morecommunication modes, is referred to herein as the “minimum lead data.”If enough data is not available as part of a lead data for the purposeincluding, but not limited to, communicating with the lead via one ormore communication modes, conducting the necessary data analysis tolearn one or more correlations among different attributes of the leaddata, and the like, additional data associated with the lead (orbusiness associated with the lead) may be retrieved/gathered fromvarious sources and added/appended to the lead data, and in such casethe term “lead data” refers to lead data including the additional data.It should be noted that such additional data may include, but is notlimited to, information about one or more technologies (such astechnology vendor name, technology product details, how many users usingsuch product, and the like) installed or used by the lead or thebusiness associated with the lead, intent of the lead or the users ofthe business associated with the lead to purchase specific product orservice, and the like. Based on the context, the term “lead data” mayrefer the said data associated with plurality of leads.

A dialing session, texting session, or a session to execute one or moreconnection attempts via one or more modes of communication is referredto herein as the “communication session.”

The terms “communication,” “contact,” “connection,” and “touch” are usedinterchangeably to refer to the communication (via one or more phonecall based or non-phone call based communication modes) with a customeror lead. For example, in a phone call based communication mode, the termcommunication/contact/connection/touch refers to a telephone call with acustomer or lead. In the context of a marketing activity, the term“communication,” “contact,” “connection,” and/or “touch” may refer to amarketing activity that involves communication with a customer or lead.The term “touch” as used in a context, for example, “third touch inwelcome multi-touch marketing campaign” refers to the third touchassociated with the welcome multi-touch marketing campaign (notassociating with any particular lead), however, the term “touch” as usedin a context, for example, “third touch for the lead with a leadidentifier 73813 in the welcome multi-touch marketing campaign” refersto the third touch in welcome multi-touch marketing campaignplanned/executed for the lead with lead identifier 73813.

The terms “communication attempt,” “contact attempt,” “connectionattempt,” and “touch attempt” may be used interchangeably to refer theattempt made to establish communication with a customer or lead.

The term “communication mode” or “contact mode” or “connection mode” or“touch mode” refers to the mode or way or channel or method ofcommunication. Examples of a communication mode include, but are notlimited to, a phone call, leaving a voice message, communication usingautomated phone technology such as an interactive voice response (IVR)system, sending an email, sending a text message, chat, instant message,video, short message service (SMS), multimedia messaging service (MMS),or communicating via any other voice or data (non-voice) basedcommunication mode available now or in the future.

The terms “communication attempt execution time” or “contact attemptexecution time” or “connection attempt execution time” or “touch attemptexecution time” may be used interchangeably to refer the time when theattempt is made to communicate with a customer or lead.

The terms “communication attempt data,” “contact attempt data,”“connection attempt data,” and “touch attempt data” may be usedinterchangeably to refer to one or more attributes associated with aconnection attempt. Based on the context, the term “connection attemptdata” may refer the said data associated with plurality of connectionattempts.

The terms “communication outcome,” “contact outcome,” “connectionoutcome,” and “touch outcome” may be used interchangeably to refer theoutcome of the attempt made to establish communication with a customeror lead.

The terms “communication attempt outcome data,” “contact attempt outcomedata,” “connection attempt outcome data,” “touch attempt outcome data,”and “touch outcome data” may be used interchangeably to refer to one ormore attributes associated with outcome of a connection attempt. Basedon the context, the term “connection attempt outcome data” may refer thedata associated with the outcome of plurality of connection attempts.

The term “agent based touch” refers to a touch that requires an agentduring the touch execution.

The term “non agent based touch” refers to a touch that may not requirean agent during the touch execution.

The term “system resource” refers to a system resource that is requiredfor communication with a customer, which may include, but not limitedto, computer system, phone system, network bandwidth, and the like.

The term “system resource data” refers to one or moreattributes/characteristics associated with a system resource. Based onthe context, the term “system resource data” may refer such dataassociated with plurality of system resources.

The term “system resource availability data” refers to one or moreattributes/characteristics associated with time availability of a systemresource (to perform a function referenced in the context). Based on thecontext, the term “system resource availability data” may refer the saiddata associated with plurality of system resources.

The term “multi-touch marketing campaign” or “MTMC” refers to a planthat enables planning and execution of one or moretouch/contact/communication with a lead.

The term “communication assistance module” refers to a module thatpartially or fully automates communication attempt associated with acustomer that gets transferred, wherein the communication assistancemodule partially of fully automates the communication attempt associatedwith the customer until the communication with the customer meets aspecific criteria, and wherein upon the specific criteria is met thecustomer gets transferred. For example, the communication assistancemodule may partially or fully automate the function of a dialing agent(in the case of phone call based communication) or a texting agent (inthe case of text based communication).

The term “prioritization information” refers to information that may beused to determine the priority or the order of a customer record forcontacting via one or more communication modes, wherein theprioritization information may be located in one or more fieldsassociated with the customer record. The term “user update fields”refers to one or more fields associated with a customer record that anagent may be allowed to update.

The term “when-to-call field” refers to one or more fields associatedwith a customer that specifies whether to contact a customer associatedwith the customer record during a specific time period or not to contactduring the specific time period, via one or more communication modes.

The term “third party communication participant” refers to a person thatparticipates in the communication between an agent and a customer. Forexample, in the case of phone call based communication, the third partycommunication participant may participate in the phone call between anagent and a customer.

As used in this document, the term “optimal” refers to anexpected/predicted optimal outcome/result, and such outcome/result mayor may not be optimal in actuality. For example, the term “optimal” asin “ . . . the order of the leads for executing connection attempts maybe predicted to yield optimal connection attempt outcomes” refers to thepredicted order to yield optimal connection attempt outcomes (for agiven circumstance based on the data availability and computer learningmethod utilized), however, in actuality the predicted order may or maynot be yielding optimal connection attempt outcomes. For anotherexample, the term “optimal” as in the context “ . . . predicting . . .optimal time period to schedule one or more communication sessions for agiven list of leads” refers to predicting the time period to executecommunication sessions that may yield optimal connection attemptoutcomes (for a given circumstance based on the data availability andcomputer learning method utilized), however, in actuality such timeperiod may or may not be yielding optimal connection attempt outcomes.For yet another example, the term “optimal” as in “ . . . computerlearning method that predicts the output with optimal accuracy” refersto a computer learning method to predict the output with optimalaccuracy (for a given circumstance based on the data availability andcomputer learning method utilized), however, in actuality such predictedoutput may or may not be optimal.

FIG. 1 is a schematic diagram illustrating a system 70 which is avariation of system 10 (FIG. 1) disclosed in the U.S. patent applicationSer. No. 13/278,764, wherein the system 70 utilizes phone call basedcommunication and text based communication, and wherein one or moredialing agents/texting agents assist the talker/texting rep tocommunicate with one or more customers via phone call or text basedcommunication.

Referring to FIG. 1, the system 70 includes dialing agent computers 20A,20B, 20C having dialing agent software stored therein, dialing agenttelephones 22A, 22B, 22C, texting agent computers 51A, 51B, atalker/texting rep computer 24 having talker/texting rep software storedtherein, a talker telephone 26, a central data server 100, a centralcommunication server 150, customer telephones 200A, 200B, 200C to handlephone calls, and customer communication devices 250A, 250B to handletext based communication.

It should be noted that a computer may be any device having a memory andprocessor, and being able to store therein functionality associated withsoftware. Examples of computers may include, but are not limited to, adesktop computer, a portable computer such as a laptop computer, tabletcomputer, smartphone, smartwatch, or a personal data assistant. FIG. 2is a block diagram further illustrating a general purpose computer. Itshould be noted that functionality of the present system and method canbe implemented in software, firmware, hardware, or a combinationthereof.

Returning to FIG. 1, within the system 70 there may be one or more thanone dialing agent computer 20A, 20B, 20C, dialing agent telephone 22A,22B, 22C, talker computer 24, talker telephone 26, central data server100, central communication server 150, and/or customer telephone 200.For exemplary purposes, FIG. 1 illustrates three dialing agent computers20A, 20B, 20C, three dialing agent telephones 22A, 22B, 22C, and threecustomer telephones 200A, 200B, 200C.

In accordance with the present invention, a telephone/phone can be atraditional analog hardware telephone, digital hardware telephone, asoftware telephone (such as session initiation protocol (SIP) clientsoftware), or the like that may be used to communicate human voice andenable phone conversation. Since the capability of a telephone maypotentially be implemented using a piece of software executed in acomputer, the telephone and computer need not be two different devicesand instead, both can be incorporated within one computer device.

The central communication server 150 may be a communication server thathas the capability of enabling phone call based communication and textbased communication. For example, to enable phone call basedcommunication, the central communication server 150 may have thecapability to perform switching functions based on commands receivedthrough CTI (Computer Telephony Interface) or software based PBX, or thelike; to enable text based communication, the central communicationserver 150 may have capability to send and receive text messages in sucha way that enables text based communication taking place between partiesas described in this document.

The central data server 100 may contain components similar to acomputer, such as, but not limited to, a memory 310 (FIG. 2), aprocessor 302 (FIG. 2), a local bus or interface 306 (FIG. 2),input/output devices 306 (FIG. 2), and a storage device 304 (FIG. 2). Adetailed description of a generic computer structure is provided hereinbelow. Of course, the storage capability and structure of the storagedevice within the central data server 100 may be different from that ofa standard generic computer storage device, however, one having ordinaryskill in the art would know such structure and differences. Inaccordance with the first exemplary embodiment, the central data server100 may store therein a list of customers for contacting, as well asdata regarding the customers. Such data may include data that istypically used in marketing such as, but not limited to, account name,contact name, address, phone number, date last contacted, notesregarding results of the last communication, and other relevantattributes.

Since the capability of the central communication server 150 could beimplemented using software executed in a computer, the central dataserver 100 and central communication server 150 need not be twodifferent devices and instead both could be in one computer.

Telephone communication links 12, 14, and 16 may be implemented usingtraditional analog telephone lines or digital telephone lines utilizingvarious digital communication protocols such as SIP, PRI (Primary RateInterface), or the like. The links 12, 14, and 16 may also be wireless,for example, but not limited to, WiFi, BlueTooth, microwave, or otherwireless voice and/or data protocols. In addition, computercommunication links 11, 13, and 53 may be implemented using a LAN (LocalArea Network), a WAN (Wide Area Network), mobile network, or the like. Acentral server communication link 15 may also be provided forcommunication between the central data server 100 and the centralcommunication server 150. The central server communication link 15 canbe implemented using computer communication links or phone communicationlinks described above. Based on implementation preferences and based onthe type of device used by texting agent 51, communication link 53 maybe implemented using a computer communication link or phonecommunication link. Based on implementation preferences and based on thetype of communication device 250 used by customer, communication link 17may be implemented using computer communication link or phonecommunication link.

One having ordinary skill in the art would understand the various typesof devices, types of telephone communication links, and computercommunication links that could be used in a system 70 (FIG. 1) embodyingthe present invention, and that other such devices and links may beprovided.

FIG. 2 is a block diagram further illustrating a general purposecomputer 300. Generally, in terms of hardware architecture, as shown inFIG. 2, the computer 300 includes a processor 302, memory 310, storagedevice 304, and one or more input and/or output (I/O) devices 306 (orperipherals) that are communicatively coupled via a local interface 308.The local interface 308 can be, for example but not limited to, one ormore buses or other wired or wireless connections, as is known in theart. The local interface 308 may have additional elements, which areomitted for simplicity, such as controllers, buffers (caches), drivers,repeaters, and receivers, to enable communications. Further, the localinterface 308 may include address, control, and/or data connections toenable appropriate communications among the aforementioned components.

The processor 302 is a hardware device for executing software,particularly that stored in the memory 310. The processor 302 can be anycustom made or commercially available processor, a central processingunit (CPU), an auxiliary processor among several processors associatedwith the computer 300, a semiconductor based microprocessor (in the formof a microchip or chip set), a macroprocessor, or generally any devicefor executing software instructions.

The memory 310 can include any one or combination of volatile memoryelements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM,etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape,CDROM, etc.). Moreover, the memory 310 may incorporate electronic,magnetic, optical, and/or other types of storage media. Note that thememory 310 can have a distributed architecture, where various componentsare situated remote from one another, but can be accessed by theprocessor 302.

The software 350 in the memory 310 may include one or more separateprograms, each of which contains an ordered listing of executableinstructions for implementing logical functions of the system, asdescribed below. As an example, in the case of the dialing agentcomputer 20A-C, the software 350 would contain an ordered listing ofexecutable instructions for implementing logical functions required ofthe dialing agent computer 20A-C, as described below. In addition, inthe case of the talker computer 24, the software 350 would contain anordered listing of executable instructions for implementing logicalfunctions required of the talker computer 24, as described below.Further, in the case of the central data server 100, the software 350would contain an ordered listing of executable instructions forimplementing logical functions required of the central data server 100,as described below.

It should be noted that in accordance with an alternative embodiment ofthe invention, software of the dialing agent computers 20A-C (FIG. 1),software of the talker computer 24 (FIG. 1), and software of the centraldata server 100 (FIG. 1) may instead be one software package havingseparate modules to perform functionality of the dialing agent computer20A-C (FIG. 1), the talker computer 24 (FIG. 1), and the central dataserver 100 (FIG. 1), respectively.

Although not required, it is possible for the memory 310 to contain anoperating system (O/S) 312. The operating system 312 essentiallycontrols the execution of computer programs and provides scheduling,input-output control, file and data management, memory management, andcommunication control and related services.

Functionality of the computer may be provided by a source program,executable program (object code), script, or any other entity containinga set of instructions to be performed. When a source program, then theprogram needs to be translated via a compiler, assembler, interpreter,or the like, which may or may not be included within the memory 310, soas to operate properly in connection with the O/S 312. Furthermore,functionality of the computer can be written as (a) an object orientedprogramming language, which has classes of data and methods, or (b) aprocedure programming language, which has routines, subroutines, and/orfunctions.

The I/O devices 306 may include input devices, for example but notlimited to, a microphone, a keyboard, mouse, scanner, joystick or otherinput device. Furthermore, the I/O devices 306 may also include outputdevices, for example but not limited to, a display, or other outputdevices. The I/O devices 306 may further include devices thatcommunicate via both inputs and outputs, for instance but not limitedto, a modulator/demodulator (modem; for accessing another device,system, or network), a radio frequency (RF) or other transceiver, atelephonic interface, a bridge, a router, or other devices that functionboth as an input and an output.

When the computer 300 is in operation, the processor 302 is configuredto execute the software 350 stored within the memory 310, to communicatedata to and from the memory 310, and to generally control operations ofthe computer 300 pursuant to the software 350. The software 350 and theO/S 312, in whole or in part, but typically the latter, are read by theprocessor 302, perhaps buffered within the processor 302, and thenexecuted.

When the functionality of the computer is implemented in software, as isshown in FIG. 2, it should be noted that the functionality can be storedon any computer readable medium for use by or in connection with anycomputer related system or method. In the context of this document, acomputer readable medium is an electronic, magnetic, optical, or otherphysical device or means that can contain or store a computer programfor use by or in connection with a computer related system or method.The functionality can be embodied in any computer-readable medium foruse by or in connection with an instruction execution system, apparatus,or device, such as a computer-based system, processor-containing system,or other system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Inthe context of this document, a “computer-readable medium” can be anymeans that can store, communicate, propagate, or transport the programfor use by or in connection with the instruction execution system,apparatus, or device.

The computer readable medium can be, for example but not limited to, anon-transient electronic, magnetic, optical, electromagnetic, infrared,or semiconductor system, apparatus, device, or propagation medium. Morespecific examples (a non-exhaustive list) of the computer-readablemedium would include the following: an electrical connection(electronic) having one or more wires, a portable computer diskette(magnetic), a random access memory (RAM) (electronic), a read-onlymemory (ROM) (electronic), an erasable programmable read-only memory(EPROM, EEPROM, or Flash memory) (electronic), an optical fiber(optical), and a portable compact disc read-only memory (CDROM)(optical). Note that the computer-readable medium could even be paper oranother suitable medium upon which the program is printed, as theprogram can be electronically captured, via for instance opticalscanning of the paper or other medium, then compiled, interpreted orotherwise processed in a suitable manner if necessary, and then storedin a computer memory.

In an alternative embodiment, where the functionality of the computer isimplemented in hardware, the functionality can be implemented with anyor a combination of the following technologies, which are each wellknown in the art: a discrete logic circuit(s) having logic gates forimplementing logic functions upon data signals, an application specificintegrated circuit (ASIC) having appropriate combinational logic gates,a programmable gate array(s) (PGA), a field programmable gate array(FPGA), or other technologies.

As mentioned previously, system 70 (FIG. 1) described herein is avariation of the system 10 (FIG. 1) disclosed in the U.S. patentapplication Ser. No. 13/278,764. It should be noted that there are manyembodiments of the system 10 (FIG. 1) of the U.S. patent applicationSer. No. 13/278,764 that have been disclosed in the U.S. patentapplication Ser. No. 13/278,764 and the U.S. patent application Ser. No.14/204,505 and all those embodiments are incorporated herein byreference, for the purpose of avoiding repetition of those embodimentsherein.

In an exemplary embodiment of the system 70 (FIG. 1) that utilizes phonecall based communication, a central data server 100 (FIG. 1) may selectan initial batch of customer records for dialing/calling form a customerlist and transmits such batch to a talker computer 24 (FIG. 1), andselects one or more customer records (associated with a customer) andtransmit to a dialing agent computer 20A-C (FIG. 1) for dialing. Uponthe central data server 100 (FIG. 1) selects (or queues) a customer fora dialing agent computer 20A-C (FIG. 1) to dial or upon the dialingagent computer 20A-C (FIG. 1) starts dialing the said selected customer,the talker computer 24 (FIG. 1) distinguishes one or more customerrecords associated with the said customer, in a first manner, for thepurposes of notifying a talker associated with the talker computer 24(FIG. 1) about the customer that has been selected or queued up fordialing (or started dialing) by a dialing agent associated with thedialing agent computer 20A-C (FIG. 1) and thereby the talker may be ableto prepare, in anticipation of the call getting answered by the customerand transferred from being between the dialing agent and the customer tobeing between the talker and the customer, by reviewing customerrecords, activity notes history, and other relevant informationassociated with the said customer, and the like. Upon the dialing agentassociated with the dialing agent computer 20A-C (FIG. 1) navigating thephone call (made to contact the said customer) through gatekeeper(s),phone tree(s), voice mail(s), and the like and reaching a live customer(the said customer that has been dialed/called) answering the phone, thedialing agent may transfer the phone call from being between the dialingagent and the customer to being between the talker associated with thetalker computer 24 (FIG. 1) and the customer. Upon the said phone callbeing transferred to the talker, the talker computer distinguishes oneor more customer records associated with the customer that has beendialed/called has been transferred, in a second manner, for the purposeof notifying the talker about the customer that has been transferred. Itshould be noted that, at any given time, the list of customer recordsand customer data transmitted to or shown on the dialing agent computer20A-C (FIG. 1) may or may not be the same as that transmitted to orshown on the talker computer 24 (FIG. 1). Upon completing the dialing ofa portion of the batch of customers, the central data server 100(FIG. 1) may select the next batch of customer records for dialing andtransmit such next batch to the talker computer 24 (FIG. 1) (and thiscycle may continue until the entire customer list is exhausted or thedialing session ends). Upon receiving each batch of customer records fordialing/calling, talker computer 24 (FIG. 1) may append that batch withthe previously shown customer records. Based on implementationpreferences, to keep computer memory utilization low, the previouslydialed/called customer records (that are no longer needed to stay in thedialing agent computer 20A-C (FIG. 1) and/or the talker computer 24(FIG. 1)) associated with previously dialed/called customers may beremoved from the dialing agent computer 20A-C (FIG. 1) and/or talkercomputer 24 (FIG. 1). It should be noted the word “dialing” and“calling” may mean the same thing and may be used interchangeably. Basedon implementation preferences, in the foregoing embodiment, a firstcomputer may transmit a notification to a second computer for thepurposes of the second computer identifying/distinguishing one or morecustomer records associated with a customer, wherein the saidnotification comprises of: one or more customer records, or one or moreunique identifiers associated with the one or more customer records, ora unique identifier associated with the customer.

One having ordinary skill in the art would appreciate that a smartphone, tablet, laptop, smart TV, smart display in a vehicle (forexample, a car), and the like (referred to herein as the “mobilecomputer”) may be used to execute one or more components of the System70 (FIG. 1) and the system described by the present invention. Further,one or more of the mobile computers may be used to in conjunction withother one or more computers to provide the functionality that interactswith one or more users (such as talker, dialing agent, texting rep,texting agent, agent, another user, and the like) of the system 70(FIG. 1) and the system described by the present invention.

It should be noted that one or more features or advantages of thepresent invention (described in a context of one or more embodiments oroutside a context of an embodiment) may be implemented: (i) as a moduleto be part of an embodiment of the System 70 (FIG. 1), or (ii) as aseparate stand-alone embodiment without one or more features/advantagesof the System 70 (FIG. 1). Further, reference to a particular feature oradvantage in the context of an embodiment may or may not be applicableto another embodiment, and one or more features or advantages of thepresent invention may be combined in any appropriate manner in anembodiment.

One having ordinary skill in the art would appreciate that the presentinvention may be practiced without one or more features or advantagesmentioned herein, and may be practiced as part of another system ormethod outside the invention mentioned herein. Further, one or moremethods described herein may be embodied as a hardware, firmware, orsoftware (stored in computer device or stored in computer readablemedium that enables execution of the software) to perform actions toaccomplish the described one or more methods.

It should be noted that any process descriptions or blocks in flowchartsshould be understood as representing modules, segments, portions ofcode, or steps that include one or more instructions for implementingspecific logical functions in the process, and alternativeimplementations are included within the scope of the present inventionin which functions may be executed out of order from that shown ordiscussed, including substantially concurrently or in reverse order,depending on the functionality involved, as would be understood by thosereasonably skilled in the art of the present invention. In addition, itmay be the case that a function may be skipped.

Based on the type of technology used for communication between any twocomponents of the system associated with the present invention andchoice of the method used for embodying the current invention, acomponent may act only as a client or may act only a server or may actas both a client and a server. Based on implementation preferences, thefunctions performed by each component of the system (including but notlimited to, central data server, central voice server, talker software,and dialing agent software) could be restructured by removing a specificfunction (whole function or a portion of a function) from one componentand delegating such function to be performed by another component.

One having ordinary skill in the art would appreciate that the system 10(FIG. 1) disclosed in the U.S. patent application Ser. No. 13/278,764may utilize one or more modes of communication with a customer involving(i) a mode of communication that requires communication to take place inreal time or near real time (such mode of communication is referred toherein as the “Real Time Based Communication”), and/or (ii) a mode ofcommunication that may not require the communication to take place inreal time or near real time (such mode of communication is referred toherein as the “Non Real Time Based Communication”). A mode ofcommunication that may not require real time or near real time mayinclude, but is not limited to, a communication mode that involvespre-recorded voice message, pre-recorded video message, short messageservice (SMS), multimedia messaging service (MMS), text, chat, instantmessage, email, other type of electronic message based communication,any other communication mode that does not require the communication totake place in real time (or near real time) that is available now or inthe future, or the like, or any combination thereof. An example of RealTime Communication is phone call based communication, such as a voicebased phone call. An example of Non Real Time Communication istext-based communication.

Returning back to FIG. 1 described herein, the system 70 (FIG. 1) mayutilize Real Time Communication modes and Non Real Time Communicationmodes. For reference purposes, communication with a customer via phonecall is referred to herein as the “Phone Call Based Communication.” TheSystem 70 (FIG. 1) that uses a phone call to connect with a customer isreferred to herein as the “Phone Call Based System 70.” The System 70(FIG. 1) that uses Real Time Based Communication to connect with acustomer is referred to herein as the “Real Time Based CommunicationSystem 70.” The System 70 (FIG. 1) that uses Non Real Time BasedCommunication to connect with a customer is referred to herein as the“Non Real Time Based Communication System 70.” In an embodiment of thesystem 70 (FIG. 1) that utilizes phone call based and non-phone callbased communication, the central communication server 150 may be used toestablish communication via one or more phone call based or non-phonecall based communication modes. One having ordinary skill in the artwould appreciate that when there is a reference to the central voiceserver 150 in FIG. 1 of U.S. patent application Ser. No. 13/278,764, ina context of non-phone call based communication, it refers to: (i) thecentral voice server (150) in FIG. 1 of U.S. patent application Ser. No.13/278,764 having capability to establish communication via non-phonecall based communication mode that is referred in the context, or (ii) acentral communication server (150) in FIG. 1 described herein havingcapability to establish communication via non-phone call basedcommunication mode that is referred in the context.

For the purposes of providing an example and ease of understanding, aNon Real Time Based Communication System 70 (FIG. 1) that utilizes textmessage based communication is described below. In a Non Real Time BasedCommunication System 70 (FIG. 1) using a text message basedcommunication to connect with a customer, a dialing agent thatcommunicates via text (instead of phone call or in addition to phonecall) may be more appropriately referred to herein as the “textingagent” and a talker that communicates via text (instead of phone call orin addition to phone call) may be referred to herein as the “textingrep.” A device or software module or application that enables a textingagent, texting rep, or another user of the system to send, receive,review and reply to a text message is referred to herein as the “textingmodule.” One having ordinary skill in the art would appreciate that thetexting module may be stored and executed in various computer devices,including but not limited to, smart phone, smart television, computer,laptop computer, tablet computer, and the like; and the texting modulemay be implemented as part of other software applications including butnot limited to, social networking websites and the like. It should benoted that the word “text,” “chat,” and “instant message” are usedinterchangeably to mean the same thing. One having ordinary skill in theart would appreciate that SMS, MMS, text, chat, and instant message arevariations of text message based communication. Any computer or deviceused by a texting rep that enables the texting rep to perform thenecessary function is referred to herein as the “texting rep computer,”and any computer or device used by a texting agent that enables thetexting agent to perform the necessary function is referred to herein asthe “texting agent computer.”

In an embodiment of Non Real Time Based Communication System 70 (FIG. 1)using a text message based communication, the texting agent may try toreach a customer via text message based communication and upondetermining that the customer has met certain criteria (such criteria isreferred to herein as the “Potential Transfer Criteria”) during theconnection attempt of the texting agent with the customer, the textingrep computer may receive a notification (referred to herein as the“potential transfer notification”) and the potential transfernotification enables the texting rep computer to distinguish one or morecustomer records associated with the customer that met the PotentialTransfer Criteria, in a first manner. The purpose of such distinguishingof one or more customer records may be to notify the texting rep thatduring the attempt to reach the customer, the texting agent hasdetermined that the customer has met the Potential Transfer Criteria. Itshould be noted that the Potential Transfer Criteria may be based onimplementation preferences; for example, the Potential Transfer Criteriamay include, but is not limited to, the texting agent just establishinga connection with the customer (for example, the customer has justresponded to a text message), or the texting agent has determined viatext-based communication that the customer has a budget approved but thetexting agent is yet to confirm that the purchase is approved, or thetexting agent has determined via text-based communication that thepurchase is approved but the texting agent is yet to confirm that thecustomer is ready to receive a proposal, or the like, or any combinationthereof. It should be noted that the distinguishing of one or morecustomer records associated with the customer that met the PotentialTransfer Criteria allows the texting rep to review informationassociated with the customer (including but is not limited to customerdata, activity/notes history, text message history including anyon-going text messages in the current communication session between thetexting agent and the customer, and the like) prior to a potentialtransfer of the connection from being between the texting agent and thecustomer to being between the texting rep and the customer and beprepared in anticipation of such potential transfer. Based onimplementation preferences, after the texting rep computer distinguishesa customer associated with a potential transfer notification the textingrep may have the option to request (or force) the texting agent totransfer the connection associated with the said customer to beingbetween the texting rep and the customer; such request may be notifiedto the texting agent; and texting agent may decide and transfer theconnection to being between the texting rep and the customer. Further,based on implementation preferences, in the case when the texting repforces the texting agent to transfer the connection with the customer tobeing between the texting rep and the customer, the system may generatea notification message to the texting agent and transfer the connection(without providing the option for the texting agent to decide on whetherto transfer the connection or not). It should be noted that for a giventexting rep, more than one texting agent may be attempting tocommunicate or communicating with more than one customer concurrently,and in which case there may be one or more potential transfernotifications that enable the texting rep computer to distinguishcustomer record(s) associated with the one or more customers that metthe Potential Transfer Criteria. That is, the potential transfernotification associated with each customer may be received by thetexting rep computer separately or a single potential transfernotification may have information associated with more than one customerthat met the Potential Transfer Criteria and the associated customerrecords may be distinguished from other customer records. It should benoted that based on the context the word “customer” may refer to the“one or more customer records” associated with the customer.

Further, in the foregoing embodiment, a texting agent may try to reach acustomer via text message based communication and upon determining thatthe customer has met certain criteria (such criteria is referred toherein as the “Connection Transfer Criteria”), the texting agent maytransfer the text message based connection between the texting agent andthe customer to being between the texting rep and the customer. Thedefinition of Potential Transfer Criteria should not be confused withthe definition of Connection Transfer Criteria, though there may be somesimilarities. Typically, a subset of customers that meet the PotentialTransfer Criteria may meet the Connection Transfer Criteria. However,since the criteria associated with Potential Transfer Criteria and thecriteria associated with Connection Transfer Criteria are user definedand customizable, based on implementation preferences, the set ofcustomers that meet the Potential Transfer Criteria may be same as theset of customers that meet the Connection Transfer Criteria. Returningback to the texting agent transferring the text based connection withthe customer (that met the Connection Transfer Criteria) to beingbetween the texting rep and the customer, upon such transfer, thetexting rep computer may receive a notification (referred to herein asthe “connection transfer notification”) and connection transfernotification enables the texting rep computer to distinguish one or morecustomer records associated with the customer associated with thetransfer, in a second manner. It should be noted that the ConnectionTransfer Criteria may be based on implementation preferences; forexample, the Connection Transfer Criteria may include, but is notlimited to, the texting agent just establishing a connection with thecustomer (for example, the customer has just responded to a textmessage), the texting agent determining that having the texting repcommunicate with the customer may help facilitate closing a transactionsuch as a sale, the texting agent determining that the customer has abudget approved, the customer is ready to receive a proposal, a purchaseis approved, or the like, or any combination thereof.

FIG. 3 is an exemplary screen view illustrating an interface 400provided to a texting rep, wherein two customers are distinguished in afirst manner (in this case, shaded using Regular Shade) after their textbased connectivity met Potential Transfer Criteria, and a customer thatgot transferred is distinguished in a second manner (in this case,shaded using Darker Shade) after the text based connectivity with thecustomer met the Connection Transfer Criteria, in accordance with theforegoing embodiment of the System 70 (FIG. 1) using text basedcommunication. As shown by FIG. 3, the customer record 402 associatedwith the transferred customer that met the Connection Transfer Criteriais shaded differently to differentiate from the other two customerrecords 403 and 404 associated with customers that met PotentialTransfer Criteria (and not the Connection Transfer Criteria). Inaddition, a window 408 shows the text messages communicated back andforth with the transferred customer, wherein after the transferredcustomer is transferred the texting rep composed a message “I couldoffer 15%” and ready to send to the transferred customer (which may besent by clicking the send button 410). It should be noted that thewindow 408 shows the text messages exchanged between the texting agentand the transferred customer prior to transfer as well as the new textmessage composed by the texting rep after the transfer. Based onimplementation preferences, the window 404 may be shown in the textingrep computer only after transferring the said customer associated withthe transfer. Further, “Mark (Agent)” be an identifier associated withthe texting rep and the same identifier may be shown while the textingagent communicates with a customer, since the texting agent may becommunicating with the customer on behalf of the texting rep. The line406 shows the customer record associated with the text message window408.

FIG. 4 is an exemplary screen view illustrating an interface 420provided to a texting agent, wherein two customers are distinguished ina first manner (in this case, shaded using Regular Shade) after theirtext based connectivity met Potential Transfer Criteria, and a customerwhose text based connectivity met the Connection Transfer Criteria isdistinguished in a second manner (in this case, shaded using LighterShade) after the text based connectivity with the customer met theConnection Transfer Criteria, in accordance with the foregoingembodiment of the System 70 (FIG. 1) using text based communication. Asshown by FIG. 4, two customer records 422 and 423 associated withcustomers that met Potential Transfer Criteria (and not the ConnectionTransfer Criteria) are distinguished using Regular Shade, and a customerrecord 421 associated with a customer that met Connection TransferCriteria is distinguished differently using Lighter Shade. In addition,a window 430 shows the text messages exchanged between the texting agentand a customer that met Connection Transfer Criteria (since the customerconfirmed that the budget is approved). Upon the foregoing customermeeting the Connection Transfer Criteria, the texting agent may clickthe transfer button 434 to transfer the text based connectivity frombeing between the texting agent and the customer to being between atexting rep and the customer. A window 432 shows the text messagesexchanged between the texting agent and a customer that met PotentialTransfer Criteria. It should be noted there may be another window (whichis not shown in FIG. 4) that shows the text messages exchanged betweenthe texting agent and the customer associated with customer record 423that also met Potential Transfer Criteria. The lines 426 and 428 showthe association between each text message window and the correspondingcustomer record in the tabular view. Further, “Mark (Agent)” may be anidentifier associated with a texting rep and the same identifier may beshown while the texting agent communicates with a customer, since thetexting agent may be communicating with the customer on behalf of thetexting rep. Based on implementation preferences, if there are more thanone texting reps associated with the texting session, upon transferringthe text based connection, in the foregoing situation, the system maytransfer the connection to Mark. The texting agent may send a textmessage to a customer by clicking the send button 436.

FIG. 5 is an flowchart illustrating actions performed when a textingagent computer receives one or more customer records and initiatesconnection attempts via text message, in accordance with an embodimentof system 70 (FIG. 1) utilizing text-based communication. As shown byblock 442, the texting agent computer 51 (FIG. 1) checks whether thetexting session (associated with the texting agent computer) is on hold.As shown by block 444, once the texting session is not on hold, thetexting agent computer 51 (FIG. 1), requests from the central dataserver 100 (FIG. 1) one or more customer records for attempting toconnect via text based communication. As shown by block 446, the centraldata server 100 (FIG. 1) responds to the texting agent computer bytransmitting one or more customer records for attempting to connect viatext based communication. Concurrently, based on the implementationpreferences, the center data server 100 (FIG. 1) may or may not transmitthe same one or more customer records to the texting rep computer. Asshown by block 448, the texting agent computer requests the centralcommunication server 150 (FIG. 1) to initiate text based connectionattempts with the one or more customers associated with the customerrecords received as shown by block 446. Also, the texting agent computermay distinguish the customer records associated the connection attempts.As shown by block 450, the texting agent determines whether a text basedconnectivity with a customer meets Potential Transfer Criteria. Based onimplementation preferences, such determination may be performedautomatically by the system or determined based on input from thetexting agent.

As shown by block 452, upon the text based connectivity with thecustomer meeting the Potential Transfer Criteria, the texting repcomputer distinguishes customer record(s) associated with the customerthat met the Potential Transfer Criteria in a first manner. One havingordinary skill in the art would appreciate that the foregoing functioncan be accomplished in many ways, for example, the texting agentcomputer transmits to the central data server 100 (FIG. 1) the saidcustomer record(s) or their unique identifiers and the central dataserver 100 (FIG. 1) further transmits to the texting rep computer thesaid customer record(s) or their unique identifiers, and the texting repcomputer may use the received the customer record(s) or their uniqueidentifiers to distinguish the said customer records in the firstmanner. It should be noted that the notification transmitted by thetexting agent computer may or may not be identical to the notificationreceived by the texting rep computer. Further, it should be noted thatthe term “first manner” in a context may or may not refer the same“first manner” referred in another context.

It should be noted that whenever a customer record is transmitted fromone computer/device to another, instead of transmitting the customerrecord the transmitting computer/device may transmit a unique identifierassociated with the customer record or partial attributes associatedwith the customer record, and the receiving computer/device may use suchunique identifier or partial attributes to fetch the remaining necessaryattributes of the customer record.

FIG. 6 is a flowchart illustrating actions performed by a texting agentwhen a text based connection with a customer meets Connection TransferCriteria, in accordance with an embodiment of system 70 (FIG. 1)utilizing text-based communication. As shown by block 462, the textingagent checks whether a text based connectivity with a customer meetsConnection Transfer Criteria. Based on implementation preferences, suchdetermination may be performed automatically by the system or determinedbased on input from the texting agent. As shown by block 464, upon thesaid customer meeting Connection Transfer Criteria, the texting agentcomputer initiates transfer of the text based connectivity associatedwith the said customer from being between the texting agent and thecustomer to being between a texting rep and the customer, and thetexting agent computer checks whether the texting session is on hold.Based on implementation preferences, if more than one texting repsparticipate in a texting session, then the texting session may beconsidered to be on hold only when all texting reps are busy (indicatingthat no further transfer of customers is possible), and if a saidcustomer can be transferred only to a specific texting rep, and if thattexting rep is busy, then the texting session may be considered to be onhold. As shown by block 465, upon determining that the texting sessionis on hold, the texting agent may perform certain pre-defined tasks (forexample, exchanging text messages to accomplish Allowable Delay of areasonably long period, schedule to contact back in the future, or thelike).

As shown by block 466, upon determining that the texting session is noton hold, the texting agent (using the texting agent computer) transfersthe text based connectivity with the customer that met ConnectionTransfer Criteria from being between the texting agent and the customerto being between a texting rep and the customer, and sends anotification that enables the central data server 100 (FIG. 1) toidentify the customer record(s) associated with the transferredcustomer. As shown by block 468, after the central data server 100(FIG. 1) identifies the customer record(s) associated with thetransferred customer in the foregoing step, the central data server 100(FIG. 1) may send a notification that enables the texting rep computerto identify the customer record(s) associated with the transferredcustomer and distinguish the customer record(s) differently in a secondmanner.

While FIG. 5 and FIG. 6 are provided with regard to a single textingagent, one having ordinary skill in the art would appreciate that theremay be more than one texting agent in the present system, resulting inthe steps of FIG. 5 and FIG. 6 being performed by each texting agent.

Based on implementation preferences, a texting rep or another user ofthe system may configure one or more configuration settings associatedwith the texting rep and such settings may include, but are not limitedto, a maximum number of customers that the texting rep may be able tocommunicate concurrently, a maximum number of texting agents preferablybe actively attempting to reach customers of the texting repconcurrently, a group of one or more texting agents defined by thetexting rep which may be defined based on texting agent skill (includingbut not limited to written communication skill, language skill, or thelike), a maximum number of customers that the texting agent may be ableto communicate concurrently, or the like. It should be noted that uponthe texting rep starting communication with the maximum number ofcustomers (as described in the foregoing sentence), the texting rep maybe declared to be busy indicating that no additional connection can betransferred to being between the texting rep and a customer. Further, ifall texting reps associated with a text communication session becomebusy, that text based communication session may be put on hold and nofurther connection can be transferred to being between any texting repassociated with the communication session and a customer. Based onimplementation preferences, when a texting session is on hold the systemmay or may not allow a certain number of text based communicationattempts to be initiated by one or more texting agents. Based onimplementation preferences, an authorized user of the system mayconfigure one or more configuration settings associated with a textingagent and such settings may include, but are not limited to, a maximumnumber of customers that the texting agent may be able to communicateconcurrently, the skill of the texting (including but not limited towritten communication skill, language skill, or the like), or the like.

It should be noted that the word “connectivity” or “connection” or“connect,” as it relates to a connection with a customer via text basedcommunication, refers to a text message based connectivity wherein thecustomer and a texting agent (or a texting rep) are engaged incommunication via text message communication or responding to one ormore text messages of the other in a reasonable response time customaryin text message based communication (such response time may becustomized to qualify as a reasonable response time), which may or maynot be in real time.

One having ordinary skill in the art would appreciate that the list ofcustomers that meet the Potential Transfer Criteria may be a subset ofthe list of customers texting agent(s) are trying to connect with,because all customers attempting to connect with may not be connectedand/or all customers attempting to connect with may not meet thePotential Transfer Criteria. Further, the list of customers that meetthe Connection Transfer Criteria may be a subset of the list ofcustomers the texting agents are trying to connect with, because allcustomers attempting to connect with texting agents may not be connectedand/or all customers attempted to connect with texting agents may notmeet Connection Transfer Criteria. The nature of the system and methoddescribed in the foregoing paragraph allows the time of the texting repto be used effectively. Based on implementation preferences, typically alist of customers that meet the Connection Transfer Criteria may be asubset of a list of customers that meet the Potential Transfer Criteria.However, based on implementation preferences, a list of customers thatmeet the Connection Transfer Criteria may not be a subset of a list ofcustomers that meet the Potential Transfer Criteria. As a way ofexample, a company may use a sales process that has seven steps, andupon the texting agent determining that the customer has fulfilled thecriteria specified in the first three steps the customer may beconsidered as meeting the Potential Transfer Criteria, however, onlyupon the texting agent determining the customer has fulfilled thecriteria specified in the first three steps as well as step 4 and step 5(that is, the first five steps in total) the customer may be consideredas meeting the Connection Transfer Criteria. It should be noted, in theforegoing example, after transferring the connectivity between thetexting agent and the customer to being between the texting rep and thecustomer the texting rep may complete the remaining two steps (step 6and step 7) successfully and completing the sales process. Further, itshould be noted that based on implementation preferences, in theforegoing example, after completing the first five steps of the salesprocess, if the texting rep is busy (and the texting agent may not beable to transfer the connection to being between the texting rep and thecustomer) the texting agent may be allowed to continue to complete step6 and then attempt to transfer the connection with the customer to beingbetween the texting rep and the customer (or, if the texting rep isstill busy the texting agent may be allowed to complete the remainingstep 7 also and complete the sale process, in which case the connectionbetween the texting agent and the customer may never be transferred tobeing between the texting rep and the customer).

It should be noted that based on implementation preferences, thePotential Transfer Criteria may involve just attempting to connect withthe customer, and in which case upon the texting agent attempting toconnect with the customer the potential transfer notification may bereceived by the texting rep computer. Further, the Potential TransferCriteria may involve just connecting with the customer, and in whichcase upon the texting agent connecting with the customer (for example,the customer has just responded to a text message) the potentialtransfer notification may be received by the texting rep computer.Further, based on implementation preferences, the Connection TransferCriteria may involve just connecting with the customer, and in whichcase upon the texting agent connecting with the customer (for example,the customer has just responded to a text message) the connectiontransfer notification may be received by the texting rep computer.

One having ordinary skill in the art would appreciate that, based onimplementation preferences, in a Phone Call Based System 70 (FIG. 1) theskill or cost associated with a dialing agent may be lower or equal towhen comparing to the skill or cost associated with a talker, and in aNon Real Time Based Communication System 70 (FIG. 1) the skill or costassociated with a texting agent may be lower or equal to when comparingto the skill or cost associated with a texting rep.

There are inherent pros and cons of using non-phone call basedcommunication. For example, based on conventional knowledge, chattingand texting may give adequate time for a sending person to draft whatthe sending person wants to say (in contrast to a phone or face to faceconversation or video conference). Further, when drafting a reply on achat, the receiving person may see the sending person is in the processof thinking and drafting a text message since the receiving person maysee something like “(sender name) is typing” or “ . . . ” as the sendingperson writes and before hitting enter. The foregoing behavior of chatmay be beneficial since it eases anxiety of the receiving person byknowing that the response will be forthcoming shortly and also the factthe receiving person is not seeing as the sending person is typing everycharacter. However, when the sending person deletes the draft messageand does not send that message the receiving person may know about thesending person changing mind and deleting the message. It should benoted that based on implementation preferences, the foregoing behaviorof the chat communication may be changed by implementing the system notto notify that the sending person is drafting a reply message and onlydeliver the message after the sending person confirms to send themessage.

It should be noted that typically in a connection established with acustomer using phone call in a Phone Call Based System 70 (FIG. 1), thedialing agent or the talker associated with the phone call basedconnection with a customer may need to respond back to the customerquickly without noticeable delay (or silence) for the purposes ofavoiding any negative perception the customer may develop otherwise.However, in a connection established with a customer using a Non RealTime Based Communication, due to the non-real time nature of thecommunication mode there may be an inherent flexibility including, butis not limited to, allowing a response with a reasonable delay, allowingmulti-tasking, and the like.

As a way of example, a texting agent or texting rep may be able tohandle more than one connection with customers concurrently. It shouldbe noted that all of such connections may be non-phone call based and/orone of such connection may be phone call based. As a way of anotherexample, when using text message based communication, the texting agentor the texting rep may be able to respond to a text message from acustomer after a delay of one or more seconds or minutes that may notaffect the customer's perception negatively. As a way of illustratingthe non-real time nature of text based communication, exemplary textmessages in a communication between a texting agent and a customer areprovided below with timestamps, wherein the customer responded to thetexting agent within a minute delay and however the texting agent'sfurther response got delayed by 3 minutes (which may be needed since thetexting agent had to validate the response message with someone else orthe texting agent may be busy in dealing with more than one connectionwith more than one customer concurrently). Such delay may be acceptablewithout affecting the customer's perception in a text-basedcommunication; however such delay may not be acceptable in a phone callbased communication.

Texting agent: Are you ready to purchase Pro version of the product?

(Sent by texting agent at 3:22 pm EST on Tuesday)

Customer: Will you be able to get 20% discount on the price youproposed?

(Received by texting agent at 3:23 pm EST on Tuesday)

Texting agent: I could offer 15% discount if you purchase today.

(Sent by texting agent at 3:26 pm EST on Tuesday)

When the texting agent wants to transfer the connection between thetexting agent and a customer to being between the texting rep and thecustomer, the texting rep may not be available to accept such transfer.In such circumstance, the inherent flexibility associated with thepossibility of delayed response from the texting agent may allow thetexting agent wait for a period of time (referred to herein as the“Allowable Delay”) until the texting rep becomes available and thentransfer the connection. An Allowable Delay of reasonably short periodmay be accomplished by not responding to the customer for a short timethat may not affect customer's perception negatively and an AllowableDelay of reasonably long period may be accomplished by executing apre-determined script (that is, sending one or more pre-determinedmessages) that makes the customer wait without ending the connection.For example, an Allowable Delay of reasonably long period may beaccomplished by having a texting agent send one or more text messagesincluding but is not limited to, “let me take few minutes to review theprevious proposal I sent,” “I am trying to figure out whether I can giveyou more discount,” “I am waiting for my manager's response to approvean additional 5% discount,” or the like. If a connection is transferredto the texting rep after the Allowable Delay of a reasonably longperiod, the texting rep may review the previous text messages (includingbut not limited to the text messages used to accomplish the AllowableDelay) and start the communication between the texting rep and thecustomer in such a way that the customer may not perceive/sense that atransfer of connection took place from the texting agent to the textingrep. In the event, after accomplishing an Allowable Delay, if thetexting agent may not be able to transfer the connection due tounavailability of texting rep, the texting agent may accomplishscheduling a follow-up communication event (via text, voice, or othercommunication modes) between the texting rep and the customer, byexecuting another pre-determined script. For example, a follow-up phonecall or texting connection event may be scheduled by having a textingagent send one or more text messages including but is not limited to,“My manager was planning to rollout a new discount program, I would liketo check about that and connect with you,” “Sorry, I didn't realize Ihave another meeting to attend in 2 minutes, can we schedule a connectvia phone call or text tomorrow at 10 am?,” “Sorry, I need to attendsomething that came up, can we schedule a connect via phone call or texttomorrow at 10 am?,” or the like. Based on implementation preferences,the system may be implemented to recommend one or more text messages tothe texting agent that may be used to accomplish the foregoing function,and/or Allowable Delay, and such recommended message may be generated bythe system based on intelligence (including but not limited topredictive intelligence) associated with various data, including but isnot limited to, effectiveness of one or more set of messages recommendedin the past (with the customer or across multiple customers), theresponse from the customer for the previously recommended message thatwas sent by the texting agent (if any), activity history with thecustomer, purchase history with the customer, field associated with thecustomer, or the like.

It should be noted that in a Phone Call Based System 70 (FIG. 1) atransfer of connection from between a dialing agent and a customer tobeing between a talker and the customer may not be possible with anAllowable Delay of long period, because if the dialing agentcommunicates with the customer via voice to accomplish Allowable Delayand then transfers the connection, the customer may notice the transferof connection taking from the dialing agent to a talker (wherein thecustomer noticing the transfer taking place is not acceptable). Further,the flexibility associated with the Allowable Delay may allow theimplementation of the Non Real Time Based Communication System 70(FIG. 1) wherein a texting agent in a texting session may be allowed tostart attempting to reach a customer using text-based communicationbefore a texting rep is readily available to accept a transfer of theconnection and once texting agent provides a potential transfernotification the system may select an available texting rep (authorizedto be a texting rep for the texting session) and send the potentialtransfer notification to the texting rep computer (enabling the textingrep to participate in the texting session), and upon the texting agenttransfers the connection the system may transfer the connection frombeing between the texting agent and the customer to being between thetexting rep and the customer. One having ordinary skill in the art wouldappreciate that based on the number of texting reps available for agiven texting session (and the number of concurrent connectionscurrently handled by each texting rep versus the maximum number ofconcurrent connections that may be handled by each texting rep), thesystem may allow an appropriate number of connections/connectionattempts to take place concurrently between one or more texting agentsand customers.

It should be noted that a response to a message received from a customerin a Non Real Time Based Communication System 70 (FIG. 1) usingemail-based communication may not require as quick a response to amessage received from a customer in a Non Real Time Based CommunicationSystem 70 (FIG. 1) using text-based communication. The foregoing natureof response time associated with the mode of communication furtherjustifies the need to utilize the benefit of a potential transfernotification in a Non Real Time Based Communication System 70 (FIG. 1)using text-based communication that enables the texting rep be preparedin anticipation of a potential transfer of a connection from beingbetween a texting agent and a customer to being between a texting repand the customer. It should be noted that based on a specific mode ofcommunication, including but not limited to, voice, video, text, chat,instant message, SMS, MIMS, email, or the like, there may be certainvariations in human behavior using such communication mode andaccordingly there may be certain variations in the features and benefitsof the System 70 (FIG. 1) and all such variations are anticipated by thepresent invention.

One having ordinary skill in the art would appreciate that, based onimplementation preferences, the Non Real Time Based Communication System70 (FIG. 1) may use a from-address/name associated with a texting repfor the text based communication, for the purposes of having thecommunication appear to be coming from the texting rep irrespective ofwhether the communication is taking place between a texting agent and acustomer or between a texting rep and the customer. It should be notedthat, if necessary, such from-address/name may be customized and suchcustomization may be pre-configured by a texting rep or another user ofthe system, or dynamically decided by the system before attempting toreach a customer based on one or more fields/attributes associated withthe customer. Further, if the customer responds to a text message, suchresponse text message may be received by/routed to a texting module in atext-capable device associated with the texting rep, or a texting modulein a text-capable device associated with the texting agent (includingthe texting agent automated by a module in the system, if applicable),or another module in the system, or any combination thereof, based onimplementation preferences.

It should be noted that the Non Real Time Based Communication System 70(FIG. 1) utilizing text-based communication may be implemented tomaintain one or more addresses for a customer that may be used to reachthe customer via text message communication (each such address isreferred to herein as the “text address”). Such text address may bestored in one more fields/attributes of a customer record. The systemmay recognize and keep track of whether a customer has a valid textaddress and use such information to avoid attempting to reach thecustomer if there is not a valid text address. Further, validity of atext address may be verified by various mechanisms, including but notlimited to, comparing the information associated with the text addresswith a different allowable patterns of a valid text addresses providedby different text message carriers using pattern matching techniques,sending a test text message and verifying that the text message wassuccessfully delivered or not delivered, bounced back, or if delivered,whether a response came from the customer, or the like. In the case ofsending text to the smart phone device of a customer via email-to-SMS oremail-to-MMS or email-to-text service in the United States of America,the text address may be an email address that starts with a 10-digitphone number of the customer and having the remaining characters of theemail address specified by the carrier/service provider of the customer(for example, 10digitphonenumberof thecustomer@txt.att.net). It shouldbe noted that if the system or the user of the system recognizes thatthe text address is not valid, such information indicating theinvalidity may be updated/associated with the customer record, which maybe further used to clean-up the invalid text addresses by one or moreusers of the system or by a module in the system to the extent suchclean-up is automated.

Further, the communication with a customer via text message may notrequire a texting agent or a texting rep with oral/accent/voicecommunication skill; instead it may be enough if the texting agent andthe texting rep have written communication skill in the language used tocommunicate with the customer via text message communication. That is,when using text message based communication, a texting agent or atexting rep may be able to pitch a product or service effectively byhaving capability to understand the one or more text messages sent bythe customer and knowing what to respond with via text.

The system may be implemented to predict and suggest one or moremessages that may be used by a texting agent or texting rep as aresponse, and the system may come up with such a suggestion by takinginto account various inputs, including but are not limited to, one ormore of text messages from the customer, notes history associated withthe customer, purchasing history of the customer, intelligenceassociated with one or more fields/attributes of a customer recordassociated with the customer, sales stage the customer may be in,marketing intelligence associated with the customer, effectiveness oftext messages in similar circumstances in the past, and the like. Itshould be noted that the texting agent function may be fully orpartially automated using a module in the system and in the case of thetexting agent function fully automated by the system there may not be aneed to have a human texting agent present and/or texting agent computermay not be present. Also, the texting rep function may be fully orpartially automated using a module in the system and in the case of thetexting rep function fully automated there may not be a need to have ahuman texting rep present and/or texting rep computer may not bepresent. For example, a semi-automated function may predict andrecommend a menu of stock answers based on one or more keywords(associated with common queries) received from a customer, and a textingagent (or texting rep) may select one or more of such answers forinserting into a response (and may customize, if needed and/or allowed),and once the response is composed the texting agent (or texting rep) maysend the response to the customer. Further, in the foregoing example,based on implementation preferences, such a function may be fullyautomated to select/compose an appropriate answer and automatically senda response to the customer. Further, a function may be implemented thatmay take appropriate action based on certain designated keywordsreceived from a customer, for example, if a customer message has akeyword “opt out” or “unsubscribe” the function may automatically set aflag that excludes the customer from future connection attempt viatext-based communication (and/or any other notification via textmessage) to the customer, and if the customer message has a keyword “optin” or “subscribe” the function may automatically flag the customer toenable future communication via text. Based on implementationpreferences, such a function may take action automatically or afternotifying a user and receiving acknowledgement from the user.

Based on implementation preferences, text-based communication in the NonReal Time Based Communication System 70 (FIG. 1) may be used by atexting agent or texting rep to schedule/arrange a phone call (phonecall based communication) which may be taking place between the textingrep (or texting agent) and the customer, in which case the texting rep(or texting agent) may need to have appropriate voice communicationskill and playing the role of a talker (or dialing agent) in accordancewith the System 70 (FIG. 1). In an embodiment of the System 70 (FIG. 1)utilizing phone call based and text based communication, one person mayplay the role of a texting agent and dialing agent concurrently, and oneperson may play the role of texting rep and talker concurrently, toexecute text-based and phone call based connection attempts with acustomer in the same communication session. For example, a texting agentmay connect with a customer via text-based communication, andconcurrently while the text-based connection is taking place the textingagent may attempt to connect with the customer on a phone call, andbased on implementation preferences, transfer a phone call basedconnection and/or a text-based connection from being between the textingagent and the customer to being between the texting rep and thecustomer. In the foregoing example, within the text-based connection orphone call based connection, the point in time when the texting agenttransfers the connection to the texting rep may be based onimplementation preferences. Further, based on implementationpreferences, the texting agent may switch from one communication mode toanother communication mode (instead of having more than one connectionactive at the same time).

A person having ordinary skill in the art would appreciate that apotential transfer notification received by a texting rep computerSystem 70 (FIG. 1) for the purpose of distinguishing a customer that metthe Potential Transfer Criteria, in a System 70 (FIG. 1) using textbased communication, is similar to a notification received by a talkercomputer for the purposes of distinguishing a customer that is beingdialed or to be dialed in the near future in the first exemplaryembodiment of the System 70 (FIG. 1), wherein the communication with thecustomer is phone call based. Further, a connection transfernotification received by a texting rep computer for the purpose ofdistinguishing a customer that met the Connection Transfer Criteria, ina System 70 (FIG. 1) using text based communication, is similar to anotification received by a talker computer for the purposes ofdistinguishing a customer whose call is being transferred from beingbetween a dialing agent and the customer to being between a talker andthe customer, in the first exemplary embodiment of the System 70(FIG. 1) wherein the communication with the customer is phone callbased. It should be noted that distinguishing a customer record may beperformed by one or more of many different methods such as, but notlimited to, highlighting, changing colors, blinking, circling, shading,changing the border around the customer information, showing thecustomer information in specific area of the screen, showing thecustomer information in a different screen, and pointing to customerinformation shown in the computer. It should be noted that prior totrying to reach a customer using a phone call based communication ortext based communication, or other modes of communication, it may benecessary to get prior permission from the customer if required by rulesand regulations governing such communication.

One having ordinary skill in the art would understand and appreciatethat the reasoning provided for the use of Non Real Time BasedCommunication in the System 70 (FIG. 1) may also be applicable to theuse of Non Real Time Based Communication in the system 50 (FIG. 45)disclosed in the U.S. patent application Ser. No. 14/204,505. In anembodiment of the system 50 (FIG. 45) disclosed in the U.S. patentapplication Ser. No. 14/204,505 involving Remote Coach functionality,based on implementation preferences, the Call Handler may try to reach acustomer via Non Real Time Based Communication (for example, textmessage based communication) and upon determining that the customer hasmet certain criteria (such criteria is referred to herein as the“Potential Request Criteria”) during the Call Handler's connectionattempt with the customer, the Third Party Call Participant computer mayreceive a notification (referred to herein as the “potential requestnotification”) and potential request notification enables the ThirdParty Call Participant computer to distinguish a record associated withthe Call Handler. It should be noted that the record associated with theCall Handler may include, but is not limited to, the first name of theCall Handler, the last name of the Call Handler, the status of the CallHandler, information related to the customer that the Call Handler isattempting to connect with/in communication with, other relevant fieldsassociated with the Call Handler, and the like. Further, the recordassociated with the Call Handler may further be expanded to include theone or more customer records associated with the customer that is inconnection with the Call Handler. The purpose of such distinguishing ofthe record associated with the Call Handler may be to notify the ThirdParty Call Participant that during the connection attempt to reach thecustomer, the customer has met the Potential Request Criteria which mayindicate that there is a potential for the Call Handler to request forassistance from the Third Party Call Participant to participate in thecommunication between the Call Handler with the customer. It should benoted that the texting agent and/or texting rep may play the role of theCall Handler and/or Third Party Call Participant.

It should be noted that the distinguishing of the record associated withthe Call Handler (expanded to include one or more customer recordsassociated with the customer) allows the Third Party Call Participant toreview information associated with the Call Handler and/or customer,including but is not limited to information associated with the CallHandler, customer data, activity/notes history, text message historyincluding any on-going text messages in the current communicationbetween the Call Handler and the customer, and the like, and be preparedin anticipation of a potential request for assistance. Further, itshould be noted that more than one Call Handler may be communicatingwith customers concurrently and in which case one or more potentialrequest notifications may enable the Third Party Call Participantcomputer to distinguish records associated with more than one CallHandler (and information associated with the customers that the CallHandlers are trying to connect with) associated with the potentialrequest notifications. Further, a Call Handler may request assistancefrom a Third Party Call Participant, and upon such request the ThirdParty Call Participant computer may receive a notification (referred toherein as the “participation request notification”) and a participationrequest notification enables the Third Party Call Participant computerto distinguish the record associated with the Call Handler (andinformation associated with the customer that the Call Handler hasconnected with). Upon such distinguishing, the Third Party CallParticipant may proceed to fulfil the participation request andparticipate in the connectivity between the Call Handler and thecustomer, following the relevant steps described in the system 50 (FIG.45) disclosed in the U.S. patent application Ser. No. 14/204,505.

A person having ordinary skill in the art would appreciate that: (i) aPhone Call Based System 70 (FIG. 1) may include one or more inboundcalls that are initiated by one or more customers, wherein one or moredialing agents and/or one or more talkers may be connected with acustomer via phone call based on such inbound calls, and wherein theinbound calls and/or outbound calls may be processed concurrently, and(ii) a Non Real Time Based Communication System 70 (FIG. 1) may includeone or more inbound communications initiated by one or more customersvia Non Real Time Based Communication mode, wherein the inbound and/oroutbound communications via Non Real Time Based Communication mode maybe processed concurrently. For an example of inbound Non Real Time BasedCommunication, in a Non Real Time Based Communication System 70 (FIG. 1)using text-based communication, one or more texting agents and/or one ormore texting reps may be connected with a customer via text-basedconnection, wherein the customer initiated the communication as aninbound text-based communication.

One having ordinary skill in the art would appreciate that in anembodiment of a Non Real Time Based Communication System 70 (FIG. 1)utilizing text message based communication, a texting rep (or anotheruser) may create a Service Request requesting a Vendor to deliver one ormore text messages to one or more customers or leads, and based on theimplementation preferences a preferred time to deliver the textmessage(s) may be specified in the Service Request. Based onimplementation preferences, such text message(s) may be delivered in acommunication session when the texting rep is present or when thetexting rep is not present.

It should be noted that in a Non Real Time Based Communication System 70(FIG. 1), the system may gather a variety of metrics including, but notlimited to, number of connection attempts made to a customer, number ofconnections established successfully with a customer, number ofconnections transferred, and the like. For example, in a Non Real TimeBased Communication System 70 (FIG. 1) utilizing text message basedcommunication, the system may gather a variety of metrics such as thenumber of text messages sent, number of text based connectionsestablished, number of connections transferred from being between thetexting agent and a customer to being between a texting rep and thecustomer, and the like.

One having ordinary skill in the art would appreciate, in an embodimentof system 70 (FIG. 1) or system 50 (FIG. 45) disclosed in the U.S.patent application Ser. No. 14/204,505 utilizing text basedcommunication mode, based on implementation preferences, the texting repcomputer may do one or more of the following: (i) distinguish (in afirst manner) the one or more leads that are yet to be attempted forconnection (which may be associated with one or more batches of leads orlead identifiers received) differently from the other leads, and (ii)distinguish (in a second manner) one or more leads that are currentlybeing attempted for connection or selected for connection attempt next,differently from the other leads, wherein the currently being attemptedfor connection or selected lead is part of the one or more batches.Further, if a texting agent is involved in facilitating connectionbetween a texting rep and a lead, the texting rep computer maydistinguish (in a third manner) a lead associated with a connection thatis currently being transferred from being between the texting agent andthe lead to being between the texting rep and the lead, differently fromthe other leads. The term “distinguishing a lead” may refer todistinguishing one or more lead records associated with the lead, andbased on implementation preferences distinguishing may involvehighlighting in a particular way.

Businesses create/obtain/receive one or more leads (and associated leaddata) through variety of sources including, tradeshows, webinars,marketing campaigns, cold calling, inbound phone call, referrals, webforms filled by website visitors (prospects, customers, past customers,and the like), visitor tracking data, social media, CRM system, otherrelevant information gathered from third party data sources (includingbut not limited to, credit information, industry information,information related to economic climate, and the like), and the like.Businesses have an important need to effectively follow-up with leads toaccomplish variety of customer relationship related activities for thepurposes of, including generating interest in a product/service,identifying new opportunities, making progress in the selling process,closing sale, providing services, maintaining relationships, renewinginterest in the products/services, conducting surveys, improvingcustomer satisfaction, and the like. As the volume of leads grows it maybecome increasingly challenging to effectively manage the leadfollow-ups.

Prior systems/methods may provide solutions to create/execute one ormore plans to follow-up with a lead (each such plan is referred toherein as the “contact plan”). A contact plan may include a preferredcommunication time, a preferred communication mode, a backupcommunication time, and a backup communication mode. Based on thecommunication mode used to contact/communicate with a lead, a contactplan may or may not require an agent to be available for communicatingwith the lead. As a way of an example, if the communication mode isphone call based, an agent needs to be available to talk to the leadupon the lead answering the phone, except when the implementationpreference allows such communication to take place using automatedtelephone messaging such as interactive voice response (IVR). As a wayof another example, if a communication mode is email (non-phone callbased) there may not be a need to have an agent available for suchcommunication to take place, except when the implementation preferencerequires an agent to review and acknowledge the email before sending. Asa way of yet another example, if the communication mode involves textmessaging, based on the implementation preferences, there may or may notbe a need to have an available agent for such communication to takeplace.

The prior systems and methods do not provide an effective solution toaddress one or more of the following:

-   -   i) to create and/or update a contact plan based on availability        of one or more agents required for contacting/communicating with        one or more leads,    -   ii) to create and/or update a contact plan based on availability        of one or more system resources required for communication with        leads,    -   iii) to create and/or update a contact plan based on volume of        leads to be contacted/communicated,    -   iv) to schedule/plan an agent's time based on the volume of        leads to be communicated/contacted via one or more communication        modes that require the agent's availability,    -   v) to schedule/plan for a system resource's availability based        on the volume of leads to be communicated/contacted via one or        more communication modes that require the system resource's        availability, and    -   vi) to create/update a plan that enables effective planning and        execution of more than one contact/communication/touch with a        lead.

It is desirable to have a system and method that overcomes one or moreof the foregoing limitations specified in the foregoing sections (i)through (vi), of prior systems and methods. Such a system and methodovercoming the one or more of the foregoing limitations is referred toherein as the “digital communication assistant” or “DCA” which isdescribed in detail below. Various examples and embodiments are providedto describe the foregoing limitations and how to overcome suchlimitations.

Based on the limitation of the prior systems/methods, when a lead iseligible to be contacted at a specific time using a specificcommunication mode according to a contact plan associated with the lead,if the communication mode requires an agent's availability and the agentis not available at that specific time the contact attempt may not beperformed, and in turn the business objective of contacting the lead atthat specific time may not be met. For example, the selected contactplan associated with a lead may propose to make a phone call (involvingan agent to have a live conversation with the lead) at a preferredcontact time, however, if there is a shortage of agent availability suchphone call may not take place. Such fact that the contact attempt is notperformed may be realized only after the execution time of theconnection attempt has elapsed and still the contact attempt had notbeen performed. However, in an embodiment of the DCA, the system maypredict the shortage of agent availability by analyzing agentavailability data and update the contact plan to replace a communicationmode associated with a touch that requires agent's availability (forexample, phone call) with another communication mode which may notrequire availability of an agent (for example, via email), wherein basedon implementation preferences, the update may or may not take placeafter receiving acknowledgement from a user of the system to proceedwith changing the communication mode. In the present invention, such anupdate may take place ahead of time comparing with a timeline in a priorart wherein the prior art system may need to wait to execute a touchthat request agent's availability (phone call in the foregoing example),figure out that the execution of that touch did not take place withinthe proposed time (due to agent availability shortage), and then, ifneeded, reactively change the communication mode to anothercommunication mode that does not require agent availability (email inthe foregoing example). Updating/replacing a touch proactively ahead oftime has a significant benefit because it creates an opportunity to havethe updated/replaced touch to being executed sooner than later, ifnecessary, and thereby the customer (or lead) may be engaged much moreeffectively in a timely manner (for example, in the case of replacing anagent-based phone call to a non-agent based email allows the email to bedelivered sooner instead of waiting to figure out at a later time thatthe phone call is not taking place due to lack of agent availability andthen reactively send an email). The reasoning similar to the foregoingreasoning provided for shortage of an agent's time availability may beapplicable to shortage of one or more system resources required for acommunication mode. It should be noted that the agent availability datamay be gathered from one or more sources that may provide agentavailability data such as time planning/tracking system, HR system,payroll system, an embodiment of the Scheduling App, and the like, orthe agent availability data may be predicted using a computer learningmethod by analyzing and learning historical agent availability data.

In an embodiment of DCA, a machine learning method may be used topredict the order of connection attempts to be executed among theeligible touches that are ready for execution at any given point intime, and based on the agent availability, the connection attempts maybe scheduled and/or queued up at appropriate times to yield optimalconnection attempt outcomes.

Further, in the foregoing embodiment, based on implementationpreferences, when the future agent availability data is not available orreliable, a computer learning method may be used to predict the futureagent availability and based on such predicted agent availabilityconnection attempts may be scheduled and/or queued up at appropriatetimes, to yield optimal results. It should be noted that in accordanceto the DCA, if the agent availability (predicted agent availability dataor agent availability from various sources) is not sufficient to executethe volume of connection attempts that need to be executed at a specificpoints in time, the system may update/replace one or more agent basedtouches with one or more touch modes that do not require agentinvolvement, and such update/replacement may yield optimal balancebetween agent availability and volume of agent based touches that areplanned to be executed at various points in time, which in turn mayyield optimal results. It should be noted that since theupdate/replacement of an agent based touch (that is predicted to be notexecuted in a timely manner) to a non-agent based touch may be takingplace, ahead of the time, it enables the system to take actionproactively which in turn may yield optimal outcome, for the givencircumstance. One having ordinary skill in the art would appreciate thatthe term “ahead of the time” in the foregoing sentence refers to a pointin time that is prior to a point in time when it is possible to confirmthat the execution of a previously planned agent based touch did nottake place. As a way of example, 200 leads have been scheduled to becalled via phone call on Friday at 11 am, and according to the presentinvention the system may determine ahead of time (before the said Fridayat 11 am) that only 120 leads could be called on Friday at 11 am anddecide to send an email on Thursday at 2 pm.

It should be noted that the time of an agent is a reasonably valuableresource and scheduling/planning such resource optimally to accomplishlead follow-ups effectively is of high importance. The same reasoningmay apply for the need to optimally schedule/plan system resource(s)associated with lead follow-ups.

When a lead is contacted, there may be a high probability that theoverall business goal (such as introducing a product, convincing thelead to get interested in the product, closing a sale, and the like) isnot met during that contact with the lead, and there may be a need tohave one or more future follow-ups with the lead to achieve the overallbusiness goal. Such follow-ups comprising more than one touch may not beeffectively planned/executed by a contact plan taught by the priorsystem/method. Hence, it may be desirable to have a multi-touchmarketing campaign/MTMC that enables effective planning/execution ofmore than one touch with a lead. In DCA, the term “follow-up” is notlimited to refer only the follow-up to contact a lead initially andinstead it refers to contacting the lead initially as well futurefollow-ups until the time when the lead reached a stage that no longerrequires a follow-up (for example, when a business entity/personassociated with the lead in no longer in business/alive, relationshipwith the lead is terminated permanently for the foreseeable future, andthe like). In an embodiment of DCA, an agent (or more than one agent)may concurrently perform more than one touch associated with the sameMTMC or different MTMCs. For example, based on implementationpreferences, an agent may be part of a dialing session and a textingsession concurrently. Further, a lead may be moved from one MTMC toanother MTMC based on certain criteria being met (for example, uponexecution of the last touch in a first MTMC or based on certain outcomeof a touch in the first MTMC, the associated lead may be moved to asecond MTMC). Based on implementation preferences, a lead may beassigned to more than one MTMC contemporaneously. Further, based onoccurrence of certain event or criteria being met, a touch may beskipped or replaced or the order of touches may be changed or a new MTMCbe created and the associated lead moved to the newly created MTMC(wherein such newly created MTMC may be custom for one lead or capableof having more than one lead assigned to the newly created MTMC). Itshould be noted that an MTMC is capable of having one or more leadsassigned to the MTMC.

Based on implementation preferences, in the context of a lead assignedto a MTMC, updating/replacing/skipping a touch, changing the order ofone or more touches in the MTMC, and the like refers to such actiontaking place for the referenced lead, and such action may involve movingthe lead to an appropriate MTMC that meets the requirement (if suchappropriate MTMC does not exist, a new MTMC may be created that meetsthe requirement and the lead may be assigned to the newly created MTMC).One having ordinary skill in the art would appreciate that if there isonly one lead assigned to a MTMC, based on implementation preferences,the foregoing update/action may be made directly to the MTMC associatedwith the lead (instead of creating a new MTMC or moving the lead toanother appropriate MTMC), however, if there is more than one leadassigned to the MTMC, such update to the MTMC may not be suitable due tothe fact it may affect the pattern of touches required for the otherleads that are assigned to the same MTMC. That is, more than one leadmay be assigned to the same MTMC only if the pattern of touches (numberof touches, order of the touches, each touch mode, each touch executiontime, and the like) of the MTMC is suitable to all such leads.

It should be noted that when more than one lead is assigned to a MTMC,not necessarily all such leads have the same touch as the next touch tobe executed. Also, when a lead is assigned to a MTMC, it is notnecessarily assigned in such a way to have the first touch of the MTMCto be executed as the first touch to be executed for the lead after thesaid assignment, for example, the lead may be assigned to the MTMC insuch a way that the 3rd touch of the MTMC may be executed as the firsttouch to be executed for the lead after the lead is assigned to theMTMC.

The terms “marketing campaign” and “multi-touch marketing campaign” meanthe same thing. It should be noted the term “update” as in the context“analyzing agent availability data and update . . . ” refers to updateperformed by the system automatically with or without an agent (oranother user) involved.

An embodiment of DCA may be implemented, with one or more of thefollowing functionalities:

-   -   1) Creating and/or updating of one or more MTMCs by a user,        wherein each MTMC comprises of one or more touches. Updating of        a MTMC by a user may include but is not limited to: adding or        deleting one or more touches, how many times to repeat a        particular touch based on touch outcome and time gap between        each such repetition, modifying the order of one or more        touches, and updating attributes of one or more touches such as        touch execution time, touch mode, and the like, which is further        described in the immediately following sections 1(a) and 1(b).        -   a) The system may allow a user to specify the order of the            touches within a MTMC and a preferred execution time            associated with each touch. Within that order, execution            time of a touch may be specified as follows: Touch execution            time may be specified in variety of ways such as an absolute            time, scheduled time, relative time, time range, the like,            and any suitable combination thereof. A relative time may be            specified with respect to occurrence of an event associated            with a touch or MTMC or another event in the system that may            or may not meet certain criteria (including but is not            limited to, addition/removal of a lead to a MTMC,            creation/deletion of a MTMC, creation/deletion/updating of a            lead, timer driven event, and the like). Scheduled execution            time may be based on execution of previously scheduled            touch, which may be scheduled by an agent (or user), or such            scheduled execution time may be decided by the system. An            example of time range may be, specifying an execution time            between 8 am and 8:30 am on a Friday, or between 10 minutes            and 20 minutes after the addition of a lead to the MTMC, or            36 hours after the execution of the previous touch            associated with the lead). Based on implementation            preferences, a touch may be executed ‘upon’ or ‘immediately’            or ‘concurrently’ when a lead is assigned to a MTMC, and a            touch may be executed ‘upon’ or ‘immediately’ or            ‘concurrently’ when another touch is executed.        -   b) The system may allow a user to specify the next step            action that may be executed automatically when a situation            described below arises (such situation is referred to herein            as the “non-optimal situation”):            -   i) When a specified touch cannot be performed at the                specified time or time range, for variety of reasons                including, but are not limited to, due to unavailability                of an agent or unavailability of a system resource                because of shortage of such agent or resource, the touch                attempt may not be performed, and the like.            -   ii) After specified number of touch attempts if a                required outcome is not achieved.            -   Based on implementation preferences, when a non-optimal                situation arises due to shortage of agent availability                or system resource availability, the system may generate                report(s) or send alert(s) to appropriate user(s) for                the purpose of notifying such non-optimal situation and                take appropriate next step action.            -   A next step action may be including, but is not limited                to, (i) skipping the touch associated with the                non-optimal situation and move the lead to another touch                that is part of the same MTMC or move the lead to                another MTMC, or (ii) replacing the touch associated                with the non-optimal situation with another touch. One                having ordinary skill in the art would appreciate that                there are variety of ways to select the next touch for                the non-optimal situation. Based on implementation                preferences, the next step action that involves                replacing a touch with another, such replacement of a                touch with another may be specific to a lead associated                with the non-optimal situation or to the MTMC (which may                affect multiple leads associated with the MTMC).    -   2) The system may automatically assign one or more leads to one        or more MTMCs, based on (a) user defined criteria, and/or (ii)        agent availability data and/or system resource availability        data. For an example in the case of assigning a lead to a MTMC        based on user defined criteria, leads that have a contact phone        number with area code ‘781’ may be assigned to a specific MTMC        that has ‘email’ as the first touch with a touch execution time        of immediately. For another example, leads that have a lead        status field value ‘new lead’ and a lead source field value        ‘web’ may be assigned to a MTMC with a name “Web Lead Welcome        Campaign,” and in addition to the foregoing field values        matching, if the lead preferred communication mode field value        matches to ‘phone call’ and lead preferred communication mode        field value matches to ‘Within 2 Hours’ the lead may be assigned        to a MTMC with a name “Web Lead Welcome Campaign—Phone call—2        Hours” wherein the first touch mode is phone call and the first        execution time is within 2 hours from the time when the lead is        submitted via web form. For yet another example, leads that have        a lead status field value ‘new lead’ and a lead source field        value ‘webinar’ may be assigned to a MTMC with a name “Webinar        Lead Welcome Campaign.” For an example in the case of assigning        a lead to a MTMC based on agent availability data, a lead may be        assigned to a MTMC comprising the first touch as agent based        touch only if agent availability data indicates that first touch        may be executed in a timely manner, otherwise the lead may be        assigned to a MTMC comprising the first touch as non-agent based        that may be executed in a timely manner without waiting for an        agent's availability.    -   3) Creating and/or updating criteria involving lead        attributes/characteristics, agent attributes/characteristics,        and the like that matches one or more leads with one or more        agents. Such criteria may be used to assign a touch associated        with a lead for execution to an agent that fits the criteria,        upon the agent becoming available and the touch becoming        eligible for execution based on the touch execution time.    -   4) Creating and/or updating criteria involving touch        attributes/characteristics, agent attributes/characteristics,        and the like that matches one or more touches with one or more        agents. Such criteria may be used to assign a touch associated        with a lead for execution to an agent that fits the criteria,        upon the agent becoming available and the touch becoming        eligible for execution based on the touch execution time.    -   5) Automatically planning and/or executing an agent based touch        upon such agent based touch becoming eligible for execution and        agent availability. A touch that does not require an agent        during the touch execution may be executed without the need to        have the agent being present, however, such execution may be        based on system resource availability. It should be noted that        based on implementation preferences, upon an agent becoming        available, a touch may be scheduled to be executed immediately        at that time and execution starts. Further, if more than one        touch may be eligible based on the execution time associated        with the touch, the order of the touches may be predicted based        on touch specific outcome correlation data and/or marketing        outcome correlation data (described elsewhere) to yield optimal        outcomes.        -   It should be noted, based on implementation preferences, to            assign an agent based touch to an agent, the agent may need            to fit the criteria that matches between lead            characteristics and agent characteristics as well as fit the            criteria that matches between the touch characteristics and            agent characteristics.    -   6) Optimal Scheduling of Agents:        -   System may analyze and learn any correlation that may exist            among lead data, agent data, agent availability data, system            resource data, system resource availability data, touch            attempt data, derived touch attempt data, touch outcome            data, and overall outcome that is of interest to the            business (all such data is collectively referred to herein            as the “marketing analysis data”). Such learned correlation            information is referred to herein as the “marketing outcome            correlation data,” and such analysis and learning may            involve plurality of leads, touch modes, touch attempts,            touch outcomes, derived touch attempt data, overall            outcomes, agent attributes/characteristics and other            relevant information, agent availability data, system            resource attributes/characteristics and other relevant            information, and system resource availability data. The term            “overall outcome” refers to “outcome associated with the            overall objective/goal that is of interest to the business”            which may include but is not limited to, getting a prospect            interested in a product offering, establishing communication            with a prospect, moving a lead to a specific step in the            marketing/sales process, sale close, increase revenue,            increase market share, improving customer satisfaction, and            the like.        -   Further, based on implementation preferences, the data            analyzed may or may not have common characteristics (for            example, the analyzed data may take into account touch            attempts across more than one touch modes, touch attempts            associated with a specific touch mode in a specific MTMC or            across all MTMCs, and the like). Touch attempt data includes            but not limited to, touch mode, touch time, one or more            agent information associated with the touch (if applicable),            and one or more system resources information associated with            the touch (if applicable). If the data analyzed is            associated only with a specific touch in a MTMC without            involving overall outcomes, the marketing outcome            correlation data associated with such data is referred to            herein as the “touch specific outcome correlation data.”        -   Analysis and learning may take place for a group of leads            having certain common characteristics or no common            characteristics. One having ordinary skill in the art would            appreciate that analysis and learning may take place using a            variety of statistical methods, computational methods,            machine learning methods, or algorithmic methods. It should            be noted that the analysis and learning may be performed            repeatedly (at regular time intervals or scheduled timings)            to update the touch specific outcome correlation data and/or            marketing outcome correlation data as new data become            available.            -   a) System enables optimal scheduling of an agent's time                by taking into account that particular agent's time                availability for the execution of agent based touches,                agent availability data associated with other agents,                marketing outcome correlation data, and the number of                agent based touches that may need to be executed at                various timeslots, to yield optimal touch outcomes.                -   Agent's time may be scheduled to be part of a                    communication session, wherein agent based touches                    are performed during such communication session. For                    example, based on a specific agent's time                    availability, that agent may be available to be part                    of one or more communication sessions for a total of                    2 hours between 8 am to 12 noon a Tuesday, and the                    system may analyze the agent availability data                    associated with other agents during that time                    period, marketing outcome correlation data                    associated with that time period, and volume of                    agent based touches associated with one or more                    leads (applicable to that agent) that may need to be                    executed during that time period, and decide to                    schedule the agent's time between 8 to 8:30, 9 to                    10, and 11:30 to 12, and such scheduling may yield                    optimal performance for the said availability of the                    agent for 2 hours total. It should be noted in the                    foregoing example, without scheduling the 2 hours                    during the system suggested timeslots, if the said                    agent schedules the available 2 hours at randomly                    selected time slots that may not be yield optimal                    performance.            -   b) System may show the optimal agent availability                requirement (number of agents required) on a given                timeslot based on the number of agent based touches                (appropriate for a given group of agents with similar                characteristics) that may need to be executed according                to the execution times of touches associated with                various MTMCs, and marketing outcome correlation data.                This may allow an agent (or another user) to check the                optimal agent availability requirement for various                timeslots and make that agent's time available in                appropriate timeslots for communication session(s) to                yield optimal outcomes. If such feature is not                available, the agent may randomly make the agent's time                available to the system that may not match with the                optimal agent availability required for optimal outcome,                which in turn may lead to non-optimal scheduling of                agent's time which may yield non-optimal outcomes. It                should be noted that as an agent's time is scheduled for                a new communication session, the system may keep                updating the agent availability for various timeslots,                after taking into account the predicted number of agent                based touches to be completed by the newly scheduled                communication session.            -   c) When a communication session is taking place, for a                given touch mode, the order of the touches (associated                with one or more leads) that are ready for execution may                be dynamically updated by the system based on the touch                specific outcome correlation data, marketing outcome                correlation data, overall outcome, and correlation                between touch specific outcome correlation data and                overall outcome. Such order of execution may further be                based on user input and/or prioritization information                associated with each lead.

Based on implementation preferences, one or more of the abovefunctionality described in the above sections (1) through (6) may befully or partially automated. The following sections (i) through (v)describe examples of such automation (with or without partialinvolvement of a user of the system):

-   -   i) creating and/or updating a MTMC, as described by the above        section (1) above. Such creating/updating of the MTMC may be        based on touch specific outcome correlation data, marketing        outcome correlation data, and correlation between touch specific        outcome correlation data and overall outcome data.        -   Touch specific outcome correlation may help to update a            touch to yield optimal outcomes at that specific touch,            however, the overall outcome may or may not be optimal. For            example, the first touch in a MTMC may be sending an email            and the corresponding touch outcomes may appear to be            optimal and touch specific outcome correlation data shows            strong justification to have the email as the first touch,            however, the overall outcome may not be as good as when the            first touch is a phone call.    -   ii) creating and/or updating a criterion (instead of allowing a        user to define the criterion) to assign a lead to a MTMC, as        described by the above section 2. Such creating and/or updating        of criteria may be based on correlation learned among two or        more of the following: lead characteristics, MTMC        characteristics, touch specific outcome correlation data, and        marketing outcome correlation data.    -   iii) creating and/or updating a criteria to assign an agent        based touch to an agent, as described by the above section 3.        Such creating and/or updating of criteria may be based on        correlation learned among two or more of the following: agent        characteristics, lead characteristics, touch specific outcome        correlation data, and marketing outcome correlation data.    -   iv) executing one or more touches, as described by the above        section 4.    -   v) allowing an agent sign-in to the system without        pre-scheduling the agent's time as described by the above        section 5, and optimize the execution of agent-based touches.

In an embodiment of DCA, the system may allow a user to create/update(and/or automate such creation/updating based on correlation learnedamong two or more of the following: lead characteristics, MTMCcharacteristics, touch specific outcome correlation data, and marketingoutcome correlation data): (i) criteria that matches between leadattributes/characteristics and system resourceattributes/characteristics, and/or (ii) criteria that matches betweentouch attributes/characteristics and system resourceattributes/characteristics. Further, the system may enable automaticallyplanning and/or executing a non-agent based touch upon such non agentbased touch becoming eligible for execution and system resourceavailability. One having ordinary skill in the art would appreciate thatwhen agent availability is taken into consideration to execute an agentbased touch, based on implementation preferences, system resourceavailability may or may not be taken into consideration.

It should be noted that whenever there is a reference to the “update”function, the update function may include the delete function. Onehaving ordinary skill in the art would appreciate that an embodiment ofDCA may include criteria to match between agent characteristics and oneor more of the following: touch characteristics, MTMC characteristics,and system resource characteristics. Further, an embodiment of the DCAmay include one or more criteria including, but not limited to, criteriato match between system resource characteristics and one or more of thefollowing: lead characteristics, touch characteristics, and MTMCcharacteristics. In another embodiment of the DCA, one or more criteriamay exist that maps suitable matches among two or more of the following:MTMC characteristics, touch characteristics, lead characteristics, agentcharacteristics, and system resource characteristics.

One having ordinary skill in the art would appreciate that based onimplementation preferences, the System 70 (FIG. 1) may create and keepupdating the priority information associated with a customer, whereinthe priority information may be stored in one or more fields associatedwith the customer, and wherein the priority information may be based onthe activity history of the lead and/or marketing analysis data (definedelsewhere in this specification). Such priority information is referredto herein as the “priority information.” It should be noted that theactivity history of the customer refers to variety of activitiesassociated with the customer including, but not limited to, customeractivities tracked via a marketing system, web browsing history,whitepaper downloads, webinar attendance, tradeshow attendance, phonecall, email, text and other electronic message communication, outcomesof communication attempts via various communication modes, face-to-facemeeting, proposal sent, purchase history, how often a particular productwas purchased with what quantify and price, and the like.

All or a portion of the functionality associated with DCA may beimplemented as a module in the System 70 (FIG. 1), or as a separatestand-alone system. It should be noted that in a context referring to anembodiment of DCA, the term “system” may refer to: (i) a separatestand-alone system that embodies one or more features/benefits of DCA,or (ii) an embodiment of the System 70 (FIG. 1) wherein one or morefeatures/benefits of DCA are implemented as a module. In an embodimentof DCA as a module in the System 70 (FIG. 1), based on implementationpreferences, (i) a talker or dialing agent may act as an agent toexecute one or more phone call based touches, and (ii) a texting rep ortexting agent may act as an agent to execute one or more text-basedtouches.

In an embodiment of DCA, the system may use any information that isdirectly or indirectly associated with a lead, and perform one or moreof the following functions: (i) automatically select the lead for one ormore connection attempts, (ii) automatically select one or morecommunication modes that are predicted to provide optimal outcome ofconnection attempt, (iii) automatically start the connection attempt viaa selected communication mode, upon meeting the criteria to start suchconnection attempt via such communication mode, and (iv) the like. Thewords “any information” in the foregoing sentence refers to informationthat may include, but is not limited to, activity history informationassociated with the lead, priority information, geographical location ofthe lead based on the physical address associated with the lead,geographical location of the lead gathered from a GPS (GlobalPositioning System) that provides the recent geographical location ofthe person associated with the lead, one or more attributes/fieldsassociated with one or more lead records associated with the lead,preferred communication mode requested by the lead, other components ofthe relevant marketing analysis data, current date and time, time zoneof the lead, criteria specified by one or more users of the system forselecting the lead for connection attempt, criteria specified by one ormore users of the system for allowing the system to start a connectionattempt via a specific communication mode, and the like. It should benoted that based on a recent geographical location of a lead gatheredfrom a GPS, the system may select the lead and prioritize forcommunication attempt to engage the person associated with the lead whenthe person is in a specific geographical vicinity, wherein the saidspecific vicinity may be based on certain criteria defined by a user.Based on implementation preferences, the criteria to start a connectionattempt via a particular communication mode may include, but is notlimited to, configuration settings associated with whether the system isallowed to start a dialing session for phone call based communicationwithout the availability of an agent, configuration settings associatedwith whether the system is allowed to start a texting session withoutthe availability of a texting rep, if allowed to start a texting sessionwithout the availability of a texting rep how many concurrent connectionattempts or connections via text may take place concurrently, and thelike, and any combination thereof. As a way of an example, in anembodiment of the DCA implemented as a module in the System 70 (FIG. 1),a talker (acting as an agent) may configure the settings to allow thesystem to start a dialing session only when at least one talker isavailable for the dialing session, however, the talker may also play therole of a texting rep and the settings may allow the system to start atexting session with up to 5 concurrent connection attempts when notexting rep is available and up to 20 concurrent connection attempts foreach available texting rep in the texting session wherein each textingrep is capable of handling 2 text-based connections concurrently, or thelike.

Based on implementation preferences, in the foregoing embodiment, theremay be one or more communication sessions that are executedconcurrently, and the leads may be delivered in one or more batches toeach communication session (wherein each batch may consists of one ormore lead records or associated identifiers). One having ordinary skillin the art would appreciate, in such embodiment, if a dialing agent (ora texting agent) is involved to assist in establishing communicationbetween the talker/texting rep and the lead as part of a communicationsession, the one or more features/benefits of the System 70 (FIG. 1),such as a dialing agent/texting agent trying to connect with a lead, andupon connecting with the lead, transferring the connection from beingbetween the dialing agent/texting agent and the lead to being betweenthe talker/texting rep and the lead. Further, there may be more than onedialing agent/texting agent involved concurrently in a communicationsession to assist in establishing connection between a talker/textingrep and leads, and the talker/texting rep computer may be enabled todistinguish the one or more lead records associated with one or moreleads that are being attempted for connection or scheduled to beattempted for connection. Further, upon transferring a connection frombeing between a dialing agent/texting agent and a lead to being betweena talker/texting rep and the lead, the talker/texting rep computer maybe enabled to distinguish differently the one or more lead recordsassociated with the lead that is being transferred. It should also benoted that based on implementation preferences, the dialing agent ortexting agent function may be fully or partially automated.

One having ordinary skill in the art would appreciate that there arevariety of ways of distinguishing a record from other records including,but not limited to, highlighting, shading, changing border, blinking,showing the data in a specific area of the screen, showing the data in adifferent screen, and the like. It should be noted that the word“connection” in the foregoing paragraphs refers to connecting via acommunication mode, including but is not limited to, phone call basedcommunication, and non-phone call based communication. It should benoted that, at any given time, the current date and time may be usedalong with marketing analysis data to predict whether the chance of theconnecting with the lead is optimal at that time, which communicationmode for connecting at that time is optimal, and/or the like.

One having ordinary skill in the art would appreciate that in anembodiment of the DCA there may be more than one connection/connectionattempts utilizing more than one communication mode taking placeconcurrently.

It should be noted that the term “event” means any event that may act asa trigger including, but not limited to, timer-based trigger, criterionbeing met, and the like. An example of a criterion may be the number ofcommunication attempts exceeding 10. Based on implementationpreferences, in an embodiment of DCA, the functionality/work load may bedistributed among more than one module to update/maintain certain datain the system, for the purposes of executing the functionality of DCA ata faster speed.

As a way of another example, an embodiment of DCA may be implemented tofollow-up one or more leads once in a given time period, for example, 90days, continuously until the lead is moved to another touch or MTMCbased on occurrence of certain event or a criteria being met, asfollows: The lead is assigned to a MTMC having a first touch specifyingthat the preferred contact method is phone call, preferred executiontime is 90 days after the time when the lead reaches the first touch,wherein the time when the lead reaches the first touch is stored in aspecific attribute. Upon the criteria to start a dialing sessionassociated with an agent is met, the system selects the leads associatedwith the first touch who were last connected via phone call basedcommunication more than 89 days ago, and start dialing such selectedleads in the order of priority based on marketing analysis data andcurrent date and time. Further, in the foregoing embodiment, based onimplementation preferences, a Prior Marketing Automation System or anEnhanced Marketing Automation System (described in the U.S. patentapplication Ser. No. 14/204,505) may maintain a lead score for each leadand the system may utilize such lead score (optionally, along with otherinformation) to select a lead for connection attempt at a specific timeof the day. Upon successfully connecting with the lead via phone call,if the outcome of the phone call indicates that the lead needs to becontacted after another 90 days, the system may update to repeat thefirst touch (and this cycle of calling once in 90 days may be repeatedmany more times as necessary). It should be noted that in the foregoingembodiment, based on implementation preferences, the system may keeptrack of unsuccessful connection attempts and automatically move thelead, whose unsuccessful connection attempts exceeded a numberconfigured in the system, to another MTMC wherein the lead may beattempted for connection via non-phone call based communication modeonce in 30 days.

Further, in an embodiment of DCA, a module may be implemented thatcreates and/or keeps updating certain information, referred to herein asthe “derived information,” which may be utilized for selecting and/orprioritizing a lead for executing a touch. It should be noted thatderived information may include but is not limited to the priorityinformation, and derived information may be based on analysis of variousinformation directly or indirectly associated/relevant to a lead and/orone or more third party systems (including but not limited to, thirdparty CRM system, third party system that provides variety of marketintelligence, and the like). Further, the derived information may bestored in one or more fields and/or indexes to optimize the speed ofexecution.

One having ordinary skill in the art would understand and appreciatethat in an embodiment of DCA, the system may be configured to queue upleads associated with one or more touches and execute the one or moretouches in one or more communication sessions concurrently, tocommunicate with the leads via one or more communication modes, andoptionally the system may be implemented to have a dashboard view thatallows a user of the system to interact and manage such one or morecommunication sessions. Further, leads may be delivered in one or morebatches to each communication session (wherein each batch may consist ofone or more lead records with necessary fields to perform the touch oreach batch may consist of one or more identifiers that may be used toidentify the associated one or more lead records). It should be notedthat after a lead is delivered or queued up for an agent, based on thepace of touch execution if the system learns/predicts that the agent maynot be able to execute the connection attempts in a timely manner for alead queued up for the agent, the system may withdraw the lead from thequeue of that agent (and/or communication session) and assign to thequeue of another agent (and/or communication session). One havingordinary skill in the art would appreciate there may be more than oneagent associated with a queue or communication session. It should benoted that based on the implementation preferences, the reference to“queue up for the agent” may mean to “assign to a queue or communicationsession associated with the agent.” Further, based on implementationpreferences, leads queued up to an agent may or may not be executed aspart of a communication session. It should be noted that based onimplementation preferences, an agent's computer may be enabled to do oneor more of the following: (i) show and/or distinguish (in a particularmanner) one or more lead records associated with the leads waiting inthe queue associated with the agent differently from other lead records,(ii) allow the agent to update one or more fields (including priorityinformation fields) associated with leads waiting in the queue and/orchange the order of the leads waiting in the queue, (iii) select thenext lead for connection attempt based on the update made by the agent,and (iv) distinguish (in a another manner) the lead that is currentlyselected/assigned to the agent for connection attempt (or scheduled tobe the next) differently from the other leads. It should also be notedthat based on implementation preferences, during a communication sessionassociated with an agent, the agent may have capability to: view (orsonically sense) one or more lead records, update one or attributesassociated with a lead record (and connection attempt data, connectionattempt outcome data), and such update may change the current or futureleads associated with one or more batches and/or the order of thoseleads. Further, based on implementation preferences, upon assigning alead to an agent, the system may initiate communication automatically.One having ordinary skill in the art would appreciate that in anembodiment of DCA having more than one computers executing the one ormore functions associated with DCA, based on implementation preferencesthere may be one or more notifications taking place, wherein eachnotification may enable the one or more computers receiving suchnotification to accomplish one or more actions (for example, includingbut not limited to, receiving a lead record, showing a lead record,distinguishing a lead record, and the like).

In an embodiment of the system 70 (FIG. 1), DCA may be implemented as amodule, wherein an agent may be in a communication session and one ormore touches that are eligible for execution are assigned to such acommunication session.

It should be noted that selecting an available agent to execute a touchattempt may be implemented in more than one ways. For example, in thecase of touch mode being a phone call, the system may first make a callto the agent to establish phone communication with the agent, make acall to the lead to establish phone communication with the lead, andthen connect them together thereby allowing communication between theagent and the lead. In another way, the system may first make a call tothe lead, make a call to the lead, and then connect those two callstogether. In yet another way, the system may pre-establish a phone callconnectivity with the agent (and maintain such pre-established phoneconnectivity for the entire communication session), after making thecall to the lead the system may wait until the lead answers the phone,and then connect with the phone call with the lead with thepre-established phone call with the agent. Further, the system mayenable the agent's computer to provide necessary lead data to the agentvia visually, sonically, and other means such as sensors and/or physicalcomputer interfaces that may communicate certain message to an agent.

FIG. 7 is a flowchart illustrating actions performed when a lead isassigned to a MTMC, in accordance with an embodiment of DCA. As shown byblock 482, the lead data associated with a lead is received by thesystem. As shown by block 484, additional lead data associated with thelead is gathered and the lead data is enriched. As shown by block 486,the lead is assigned to a MTMC based on user defined criteria and/oragent availability data and/or system resource availability data.

FIG. 8 is a flowchart illustrating actions performed when atouch/connection attempt or a MTMC is getting updated proactively basedon agent availability, in accordance with an embodiment of DCA. As shownby block 502, the system checks whether sufficient agents are availableto execute a future agent based touch in a timely manner during theappropriate planned execution time. As shown by block 504, upondetermining that there is not sufficient agents available for executingthe agent based touch in a timely manner (during the appropriate plannedexecution time), the system proactively (i) updates/replaces the agentbased touch with a non-agent based touch, or (ii) if applicable, changethe order of the touches by having the agent based touch switches with anon-agent based touch.

FIG. 9 is a flowchart illustrating actions performed when atouch/connection attempt is executed, in accordance with an embodimentof DCA. As shown by block 522, the system checks whether a touch isready for execution. As shown by block 524, upon determining that thetouch is ready for execution, the system further checks whether thetouch is an agent based touch (that requires an agent's involvement forexecution, for example, phone based touch). As shown by block 532, ifthe touch is non agent based touch, the non-agent based touch isexecuted. Based on implementation preferences, before executing thenon-agent based touch the system may further check whether there isenough system resources to execute the non-agent based touch and ifaffirmative proceed to execute the non-agent touch. As shown by block526, upon determining that the touch is an agent based touch, the systemassigns the agent based touch for execution. One having ordinary skillsin the art would appreciate that such execution may be performed in avariety of ways, for example, the agent based touch may be queued to bepart of a communication session (with appropriate communication mode) inan embodiment of the system 70 (FIG. 1). As shown by block 528, thesystem checks whether the agent based touch is executed during thespecified execution time (as per the touch execution time specified bythe associated MTMC). As shown by block 530, if the system determinesthat the agent based touch has not been executed during the specifiedexecution time, the system may update/replace the agent based touch witha non-agent based touch or if applicable, change the order of thetouches associated with the MTMC by having the agent based touchswitches with a non-agent based touch.

FIG. 10 is an exemplary screen view illustrating an interface showingthe required agent availability/required number of available agents toexecute agent based touches (for optimal performance) versus the actualagent availability/actual number of available agents, for varioustimeslots, using a combination of bar and line graph, in accordance withan embodiment of DCA. As shown by FIG. 10, for each time slot on Mar.23, 2014, the actual agent availability data is shown using a thinnerline 542 and the required agent availability data is shown using athicker line 544. For example, for the time slot from 11 am to 11:30 am,the required number of agents needed is 75 (shown by 546) to execute theagent based touches during that time (and thereby yielding optimalperformance) and however only 50 (shown by 548) number of agentsactually available during that time.

The foregoing example indicates that there is a shortage of the numberagents by 25 (75 minus 50) for the said time slot. Based onimplementation preferences, in accordance with DCA functionality, thoughthe system may proactively keep updating (for example, replacing anagent based touch with a non-agent based touch, switching an agent basedtouch with a non-agent based touch) the touches in a way to maintainonly optimal number of agent based touches that can be executedsuccessfully during a time slot, the system may keep track of therequired agent availability versus actual agent availability data todraw the bar/line graph as shown in FIG. 10. It should be noted that auser of the system may use the information provided by bar/line graph asshown in FIG. 10 to adjust the actual agents available for each timeslot and thereby achieve optimal results (for example, executing therequired number of agent based touches and reducing the overall agentcost).

FIG. 11 is an exemplary screen view illustrating an interface to specifycriteria associated with lead characteristics to assign one or moreleads to a MTMC, in accordance with an embodiment of DCA. As shown byFIG. 11, the area of the screen 562 allows a user to specify thecriteria to select one or more leads (in this example, the criteriaspecified is: Area Code=978 AND State=MA AND Lead Status=New AND LeadSource=Tradeshow). The control 564 allows the user to delete thecorresponding criterion by clicking “x” or add a new criterion byclicking “+.” The selected one or more leads may be assigned to the MTMCselected/specified in the drop down list control 566.

FIG. 12 is an exemplary screen view illustrating an interface providedto a talker communicating with leads using phone call basedcommunication, wherein dialing agent functionality is fully automated,wherein the leads are selected for phone call based communication basedon talker/agent availability, in accordance with an embodiment of DCA.As shown by FIG. 12, the checkbox 582 allows a user to notify the system(by checking off the checkbox) that the user is interested in phone callbased communication session, and the user may start the session byclicking the start session button 584. The tabular view 586 shows thelist the leads that are selected and queued up for phone call basedcommunication. The lead record that is distinguished with a lightershade (shown by 588) is associated with the lead that is currently beingdialed.

FIG. 13 is an exemplary screen view an interface provided to a textingrep communicating with leads using text based communication, whereintexting agent functionality is fully automated, wherein the leads areselected for text based communication based on texting agent/agentavailability, in accordance with an embodiment of DCA. As shown by FIG.13, the checkbox 602 allows a texting rep to notify the system (bychecking off the checkbox) that the texting rep is interested in textbased communication session, and the texting rep may start the sessionby clicking the start session button 603. The tabular view 604 shows thelist the leads that are selected and queued up for text basedcommunication. The lead record that is distinguished with a lightershade (shown by 606) is associated with the lead that is currently beingcommunicated via text based communication. In addition, a window 608shows the text messages exchanged between the texting rep and the saidlead. The line 610 shows the customer record associated with the textmessage window 608. The texting rep may send a text message to the saidlead by clicking the send button 612.

One having ordinary skill in the art would appreciate that the System 70(FIG. 1) may accept updates/inputs dynamically from a user during adialing session, texting session, or communication session using adifferent communication mode. Such update/input is referred to herein asthe “user input” which may include, but is not limited to, updates toone or more fields storing information associated with priorityinformation, do-not-call, allowed-to-call, do not call until, phonenumber, update to the order of records shown in the screen, and thelike. It should be noted that based on the context the words “update”and “input” may be used to mean the same thing. The System 70 (FIG. 1)may use all or some portion of the user input to make a decision (orpredict outcomes/results) on one or more issues/matters, including butnot limited to, selecting one or more leads to make connection attemptnext, the order in which such leads may be processed to make connectionattempts, how many times to attempt to connect with such one or moreleads, an optimal time period to schedule one or more communicationsessions for a given list of leads, an optimal communication mode, andthe like (each such issue/matter/problem that requires a decision isreferred to herein as the “vital issue”). Further, the decision for avital issue may be time sensitive, that is, the decision for the samevital issue may be different at different time. For example, foryielding optimal outcomes, the order in which a list of leads may becalled at 9 am on a Tuesday may be different from the order at 10 am onTuesday. It should be noted that the communication mode utilized for aconnection attempt may be phone call based or non-phone call based.Further, it should be noted that if the system uses a non-phone callbased communication mode, any reference to the word “call” or “phonecall” may be interpreted as “connect or communicate or link using thenon-phone call based communication mode.”

A connection attempt may have one or more attributes referred to hereinas the “connection attempt data,” which may include but not limited tocommunication mode used for the connection attempt, execution time ofthe connection attempt, and information associated with an agent (oruser) that was involved in the connection attempt (if such user isinvolved or applicable). It should be noted that execution time of aconnection attempt may include all aspects of time when the connectionattempt is executed, including but not limited to, time of the day, dayof the week, week of the month, month of the year, quarter of the year,or the like. One or more attributes associated with the outcome of aconnection attempt is referred to herein as the “connection attemptoutcome data.” Examples of connection attempt outcome data may includebut not limited to: lead answered the call, went to voice mail, noanswer, wrong phone number, other connection disposition, and the like.

One or more attributes may be derived from connection attempt dataand/or connection attempt outcome data associated with a particularconnection attempt or more than one connection attempt, and such one ormore derived attributes is referred to herein as the “derived connectionattempt data.” Connection attempt data, connection attempt outcome data,and derived connection attempt data, are collectively referred to hereinas the “historical connection intelligence data” or “HCID.” It should benoted that the term “historical connection intelligence data” or “HCID”may refer to data associated with more than one connection attempt,unless specifically referring a specific connection attempt. Further, incertain contexts describing an embodiment, for the purposes ofemphasizing the inclusion of the connection attempt outcome data as partof the data referenced, it may be explicitly specified though theconnection attempt outcome data is implicitly included. Also, in certaincontexts, the connection attempt outcome data may be excluded from thedata that is being referenced by explicitly specifying such exclusion.It should be noted that HCID may be updated as new connection attemptdata becomes available.

It should be noted that the terms “communication attempt data,” “contactattempt data,” “connection attempt data,” and “touch attempt data” maybe used interchangeably to mean the same thing, and the terms “derivedcommunication attempt data,” “derived contact attempt data,” “derivedconnection attempt data,” and “derived touch attempt data” may be usedinterchangeably to mean the same thing.

Examples of lead data attributes may include, but not limited to: (i)phone area code or a geographic region the lead belongs to, (ii) aspecific industry the lead belongs to, (iii) persona (related to title,job function, and the like) of the lead, (iv) lead type (such as, B2B,B2C, and the like), (v) size of the business the lead belongs to (suchas, small, small to midsize, enterprise, and the like), and the like.

Further, in a context where more than one connection attempt is takeninto account (for example, to arrive at the derived connection attemptdata), such more than one connection attempt may be associated with thesame lead or group of leads having commonality or no commonality. As away of providing an example for a derived connection attempt dataattribute, area code may be a derived connection attempt data attributederived from a phone number attribute. For another example, connectionrate associated with a connection attempt in a particular hour may be aderived connection attempt data attribute which is calculated bydividing the number of connection attempts that resulted in establishingsuccessful connections (in the case of phone call based communication,the number of phone calls answered by the leads) during that hour withthe total number of connection attempts made during that hour. For yetanother example, meeting scheduled rate associated with a connectionattempt in a particular hour may be a derived connection attempt dataattribute which is calculated by dividing the number of connectionattempts that resulted in meetings scheduled during that hour by thetotal number of connection attempts made during that hour. In theforegoing example, based on implementation preferences, the number ofmeetings scheduled may be arrived at by counting the number of connectattempts that resulted in a connect attempt outcome/disposition having avalue of “meeting scheduled.”

One having ordinary skill in the art would appreciate that one or moremodules in the System 70 (FIG. 1) may utilize HCID and/or marketinganalysis data (defined elsewhere in this specification) to make decisionon vital issues and/or update one or more fields of the lead recordsassociated with the prioritization information. Based on implementationpreferences, the System 70 (FIG. 1) may use user input in addition toHCID and/or marketing analysis data (defined elsewhere in thisspecification), or instead of HCID to make decision on vital issues.

It should be noted that the HCID may take into account the dataassociated with connection attempts made by the System 70 (FIG. 1)and/or connection attempts made outside of the System 70 (FIG. 1). Onehaving ordinary skill would appreciate that the HCID may be derived frommarket intelligence pertaining to historical rate of connection attemptsthat resulted in establishing successful connection with leads (in thecase of phone call based communication, the number of phone callsanswered by the leads, and any associated trends. Such marketintelligence may be gathered/derived from various sources including, butnot limited to, connection attempt data obtained from the System 70(FIG. 1) and/or other third party systems.

Based on implementation preferences, one or more attributes of HCIDand/or marketing analysis data (defined elsewhere in this specification)may be used to derive intelligence that enables the System 70 (FIG. 1)to predict decisions associated with the vital issues that may yieldoptimal results. One having ordinary skill in the art would appreciatethat HCID and/or marketing analysis data (defined elsewhere in thisspecification) may be used to train one or more machine learning methodsto learn correlation/pattern/relationship among various attributes anduse such learning to predict decisions/answers to the one or more vitalissues (including but not limited to outcomes of future connectionattempts). For example, correlation between connection attempt executiontime and connection attempt outcome data for a particular communicationmode may be learned by a computer learning method and such computerlearning method may be used to predict the connection attempt outcomedata associated with various connection attempt execution times in thefuture, time to execute connection attempts to yield optimal outcomes,and the like. It should be noted that the term “machine learning method”means to include, but is not limited to, machine learning or statisticallearning method, model, algorithm, technique, approach, apparatus, andsystem; and based on the context it may refer to plurality of machinelearning methods.

The one or more attributes of HCID, marketing analysis data (definedelsewhere in this specification), and other relevant data used to traina machine learning method is referred to herein as the “training data.”One having ordinary skill in the art would appreciate that there aremany conventional machine learning methods available that may be trainedto provide prediction. Based on implementation preferences, theattributes of HCID may include other attributes (directly or indirectlyassociated with connection attempt data and lead data) that are notlisted herein and such attributes may be gathered in the System 70(FIG. 1) or from sources outside the System 70 (FIG. 1). Further, basedon implementation preferences, the information associated with anattribute may be stored in one or more fields that are stored locally orremotely (such as a computer or storage device located remotely, in thecloud, and the like) or a combination thereof, and stored in one or morestorage format, medium, and devices.

One having ordinary skill in the art would appreciate that the trainingdata may be illustrated in a matrix format having rows and columns, asfollows: One may use a notation n to represent the number of distinctobservations or instances or data points in the training data (referredto herein as the “training data instance” or “training instance”). A setof training data instances may be referred to herein as the “trainingdata set.” Each training data instance may have m number of variables orattributes that may be used in making predictions. In the context ofmachine learning method, the term “input,” “input variable” and “inputattribute” may be used interchangeably to mean the same thing, and theword “output” is meant to “output variable on which one wishes to makeprediction” based on a given input. For example, an input may have oneor more attributes associated with a future connection attempt data andthe associated lead data, the output may be the outcome of such futureconnection attempt which one wishes to predict using a machine learningmethod. It should be noted that based on implementation preferences, aset of training data instances used to train a machine learning methodmay be associated with any lead or a group of one or more leads havingcommonality or no commonality. For example, one or more leads may begrouped together having commonality such as the leads associated with aspecific industry, geographic region, or the like.

In an embodiment of the System 70 (FIG. 1), a machine learning methodmay be used to make effective predictions on vital issues including, butnot limited to, predicting which lead to select for connection attemptat a given time that has a higher probability of the connection attemptresulting in establishing a successful connection, among the leads thatare assigned or ready to be assigned to a communication session (forexample, dialing session for phone call based communication, textingsession for text-based communication, and the like). As a way ofexample, using machine learning method, if the System 70 (FIG. 1)predicts that at around 11:10 am on a Tuesday during the second week ofMay 2014, a lead that belongs to area code 781 and having a Directorlevel title may have a higher probability of answering a phone call thananother lead (for example, that belongs to area code 603 and/or havingnon-director level title), the lead that belongs to area code 781 may beprioritized and called first to achieve an optimal connection attemptoutcome. Based on implementation preferences, similar to predictingwhich lead to select for the next connection attempt, the order of theleads for executing connection attempts may be predicted to yieldoptimal connection attempt outcomes.

The goal of a supervised machine learning method is to determine afunction that predicts an output for a given instance of input, whereinthe output is a close approximation of the actual output, and whereinthe function is a close approximation of the actual function thatproduces the actual output for the given actual input. If sufficienttraining data instances are available to represent all possiblecombination of input attributes and output attributes, a computer maylearn the relationship between all possible inputs and outputs andcreate a function that matches the actual function (that produces theactual output for the given actual input). However, it may be difficultto collect all possible combination of input and output values. Hence,the computer learning method may use a smaller subset of possiblecombinations of input and output attributes to learn and create anapproximate function that may predict the output for the a given inputattributes. Such predicted output and associated input may not be partof the set of training data instances used to train the computerlearning method. When the correlation between the input and output iscomplex, it may be very difficult (or impossible) to determine theactual function. There may be number of reasons for such difficulty,including but not limited to, all input attributes that influence theoutput may not be known, known input attributes that influence theoutput may not be measured, when a known input attribute is measured thequality of such measurement may not be perfect, and the like. Hence,embodiments of the current invention provide a computer learning methodthat predicts the output with optimal accuracy.

Accuracy of a computer learning method generally depends on the accuracyof training data instances that are used to train a computer learningmethod. Further, it may be important to continuously train the computerlearning method as new training data becomes available because thecorrelation between the input and the output in training data instancesmay change over time. For example, a computer learning method that istrained with a second set of training data instances may outperform (inpredicting the future output for a given input) the computer learningmethod that is trained with a first of training data instances which wasavailable in the past. Based on implementation preferences, such newtraining data set may be utilized along with previously gatheredtraining data set (or utilized independently) to train a computerlearning method. Also, performance of various computer learning methodsmay need to be evaluated on an on-going basis with new training dataset, to select the optimal computer learning method that yields optimalprediction. For example, based on the new set of training datainstances, a computer learning method that was not previously selectedmay become the optimally performing computer learning method (whichoutperforms the previously employed computer learning method). Hence, itis desirable to have the system to keep track of how each computerlearning method is performing as new training data set is available andkeep employing an optimal computer learning method.

There may be many different sets of training data instances that may beused to train a given computer learning method and the associatedprediction accuracy may be different. For a particular computer learningmethod to analyze and learn correlation in HCID and/or marketinganalysis data (defined elsewhere in the specification), and provideprediction, following are some of the examples of set of training datainstances associated with HCID that may be used: (i) a set of trainingdata instances associated with last year August month may be the optimaltraining data set to optimally predict the connection attempt outcomesduring this year August, (ii) a set of training data instancesassociated with the week before Thanksgiving week last year may be theoptimal training data to optimally predict the connection attemptoutcomes during the week before Thanksgiving week this year, (iii) a setof training data instances associated with a specific month during theyear 2008 when the economy was going down may be the optimal trainingdata to optimally predict the connection attempt outcomes during a monthwhen the economy goes down in the future, (iv) a set of training datainstances associated with the time slot 10 to 10:30 am on WednesdayAugust 2nd week last year may be the optimal training data set topredict connection attempt outcomes same time period this year, and (v)a set of training data associated with the time slot 10 to 10:30 amaveraged over all Wednesdays of August last year may be the optimaltraining data to optimally predict connection attempt outcomes duringthe same time each Wednesday of August this year.

There may exist correlation between different sets of training datainstances that may be used to train a computer learning method and thecharacteristics associated with the time period when of the output needsto be predicted. One having ordinary skill in the art would appreciatethat for a given predicted output, over time, there is an opportunity tocompare the predicted output with actual output. A system and method maybe developed that analyzes and learns the correlation among trainingdata set, predicted output, corresponding actual output, characteristicsof the training data set, and characteristics associated with theoutput; and based on such learning predict which optimal training datamay be used to train a given computer learning method to yield optimalprediction accuracy to predict output having certain characteristics. Itshould be noted that the characteristics associated with training dataset and characteristics associated with predicted output, may include,but is not limited to, characteristics associated with the time periodwhen the training data set was collected and when the output ispredicted. For example, week before Thanksgiving week, month when theeconomy was going down, and the like may be characteristics associatedwith a time period.

Training data instances having common characteristics may be groupedtogether to create a specific set of training data instances. Suchcharacteristics may include but not limited to, leads associated with aspecific industry, leads associated with certain job titles, time periodassociated with a specific time of the day, time period associated witha specific weekday, time period associated with a specific week in ayear, time period associated with a specific month in a year, timeperiod associated with when the economy went down last time, time periodassociated with last year school vacation, and the like.

Besides many different sets of training data instances, there may bemany different of computer learning methods to consider. There ismany-to-many combination between the one or more training data and oneor more computer learning methods. It is desirable to have a system anda method that analyzes and learns any correlation among characteristicsvarious training data sets, characteristics of various outputs thatneeds to be predicted (referred to herein as the “outputcharacteristics”), and prediction accuracies of various computerlearning methods predicting the output when trained with the varioustraining data sets. Based on such learning, the system and method mayselect a computer learning method and a training data set that providesoptimal prediction accuracy for a given characteristics of output thatneeds to be predicted. Such system and a method is referred to herein asthe “computer learning method selector.” It should be noted that thecomputer learning method selector may be one or more computer learningmethods that learn the above mentioned correlation and selects/predictsthe optimal computer learning method and optimal training data set, fora given future time period. As new training data sets to train thecomputer learning method selector become available, the computerlearning method selector may need to be trained on an on-going basis tokeep improving its selection/prediction accuracy.

Returning back to derived connection attempt data, few examples ofderived connection attempt data associated for phone call basedconnection attempts are given below. For example, derived connectionattempt data may be derived by aggregating data associated with multiplecalls, the calls made during a specific time period may be taken intoaccount and such time period is referred to herein as the “AggregationTime Interval.” Further elaborating the foregoing example, in anembodiment of a computer learning method, the system mayutilize/aggregate connection attributes of calls made during anAggregation Time Interval of fifteen minutes time period on each weekdayto arrive at (i) a derived connection attempt data that indicates theratio of number of calls answered versus total number of calls made forleads whose phone numbers belong to a specific area code (for example:781), (ii) a derived connection attempt data that indicates the ratio ofnumber of calls answered versus total calls made for leads that belongto a specific area code (for example: 781) and also belong to a specificindustry (for example: “software products” industry), (iii) a derivedconnection attempt data that indicates the ratio of number of callsanswered versus total number of calls made for leads that belong to aspecific area code (for example: 781), belong to a specific industry(for example: “software products” industry), and also having a titleCEO, and the like.

Based on implementation preferences, values associated with a connectionattempt data attribute may be mapped to a set of standard values andsuch mapping may allow the creation of one or more derived connectionattempt data attributes associated with those standard values. Forexample, a lead's title may include, but is not limited to, CEO, CFO,CIO, CTO, Vice President, Director, Manager, Team leader, supervisor andthe like, however, the standard title values may be limited to 3 valuesnamely, C-Level Title, Director-Level, and Manager-Level, and eachlead's title value may be mapped to one of the 3 standard title values.Such mapping allows the creation of derived connection attempt dataassociated with the standard title values, for example, the system mayarrive at (i) a derived connection attempt data that indicates thenumber of calls answered by the leads whose title is mapped to“C-Level,” (ii) a derived connection attempt data that indicates thenumber of calls answered by the leads whose title is mapped to“Director-Level,” and (iii) a derived connection attempt data thatindicates the number of calls answered by the leads whose title ismapped to “Manager-Level.” It should be noted, based on implementationpreferences, in addition to or in lieu of the “number of calls answeredby the leads” the system may calculate/arrive at “number of calls notanswered” in the foregoing examples. Further, in addition to or in lieuof the “number of calls” the system may calculate/arrive at “percentageof calls.”

Based on implementation preferences, the system may have an option toconfigure/customize the settings associated with arriving at one or moretraining data sets. For example, such settings may include but notlimited to, Aggregation Time Interval to create derived connectionattempt data, time period associated with the training data set (forexample, HCID related to a specific calendar week), how often thederived connection attempt data may be refreshed/updated (for example,once nightly, every hour, and the like), and the like. It should benoted that the derived connection attributes may or may not be stored ina data structure different from the data structure where lead dataand/or connection attempt data may be stored. One having ordinary skillin the art would appreciate that the data structure may include, but isnot limited to, table, index, cluster, file, and the like, within adatabase or file system or another type of storage, and such datastructure may be refreshed periodically.

Numerous embodiments of the System 70 (FIG. 1) are provided below,describing variety of ways of using one or more computer learningmethods to predict answers/decisions to variety of vital issues. Onehaving ordinary skill in the art would appreciate that computer learningmethod may be utilized to predict answers/decisions to vital issueslisted herein and vital issues that are not listed herein.

In an embodiment of the computer learning method, for each lead recordin a list, the system may utilize a machine learning method to arrive ata prediction score (referred to herein as the “connect predictionscore”) that represents the probability of a connection attemptresulting in establishing a successful connection. Further, the connectprediction score may be used to order the leads for connection attempts.That is, the computer learning method may predict the order of leads forconnection attempts that may yield optional results. It should be notedthat the time of a day when a connection attempt is to be made may beone of the attributes along with the HCID and/or marketing analysis data(defined elsewhere in the specification), which is used as input by thecomputer learning method to predict the connection attempt outcomeand/or arrive at the connect prediction score. During the usage of thesystem associated with the embodiment, since the time of the day whenthe connection attempt is to be made keeps changing as time goes on, theorder of the leads for connection attempts may need to updated on anon-going basis to yield optimal connection attempt outcomes. Based onimplementation preferences, the user may be given the option of orderingthe lead records in a list, for connection attempts, based on one ormore fields of the lead records specified by the user for sort order orallowing the system to order the lead records based on the connectprediction score associated with each lead. It should be noted thatbased on implementation preferences, connect prediction score associatedwith a lead may be shown in the agent computer.

In an embodiment of the System 70 (FIG. 1), whenever the need arises toselect/predict the next lead record for making the communicationattempt, the system may determine the connect prediction score for eachlead in the list that is yet to be attempted or connected, and selectthe appropriate next lead record (for example, the lead with the highestconnect prediction score) for connection attempt, which may yieldoptimal connection attempt outcome. Further, in another embodiment ofthe System 70 (FIG. 1), instead of selecting one record at a time tomake the next connection attempt, the system may use the connectprediction score (determined/updated recently or determined/updateddynamically on the fly) to select a batch of one or more lead records(“batch selection”) at a time to make connection attempt next, whereinthe selected batch comprises of lead records with high connectprediction scores, which may yield optimal connection attempt outcomes.It should be reminded that such batch selection based implementationallows (i) the user to view and/or update one or more attributes (suchas allowed-to-call, Do Not Call Until, and the like) associated with oneor more lead records that are part of the selected batch, and (iii) ifthe system is yet to initiate a connection attempt to a lead recordassociated with the batch, any update made to the lead record may inturn enable the system to proceed with the connection attempt, not toproceed/skip the connection attempt for the lead record, not to makeconnection attempt until a specific date and time, and the like.Further, based on implementation preferences, the system may be allowedto decide the next lead record or the next batch of one or more leadrecords based on the connect prediction score, as well as, taking intoconsideration the inputs or updates (for example, provided by a user) tocertain relevant settings or lead records such as priority informationthat may indicate how many times to make connection attempts to connectwith a lead during a communication session or a specific custom timeperiod, time gap between two successive connection attempts associatedwith a lead, whether to override the system predicted order ofconnection attempts and move a lead to up or down in remaining list ofleads for connection attempts, and the like. One having ordinary skillin the art would appreciate that based on implementation preferences, inthe foregoing embodiment of the System 70 (FIG. 1), if the user isacting as a talker/texting rep and the dialing agent/texting agentfunction is fully or automated (or eliminated and having the function ofthe dialing agent/texting agent be performed by the talker/texting rep),the computer used by the user may do one or more of the following: (i)distinguish in a first manner one or more leads that are yet to beattempted for connection (and associated with one or more batches)differently from the other leads, and (ii) distinguish in a secondmanner a lead that is currently being attempted for connection orselected for connection attempt next differently from the other leads,wherein the talker/texting rep may make the connection attempt withoutassistance from dialing agent/texting agent (if dialing agent/textingagent function is eliminated), wherein the distinguished lead in thesecond manner is part of the one or more batches. In the foregoingsituation, in the case of text-based communication, there may be morethan one lead that are attempted concurrently for connection, andaccordingly the said more than one lead may be distinguished in thesecond manner. Further, if dialing agent/texting agent is involved infacilitating connection between the user (talker/texting rep) and alead, the computer used by the user may distinguish in a third manner alead associated with a connection that is currently being transferred tobeing between the talker/texting rep and the lead differently from theother leads. The term “distinguishing a lead” may refer todistinguishing one or more lead records associated with the lead, andbased on implementation preferences distinguishing may involvehighlighting in a particular way.

In a “batch selection” embodiment, if the batch size is large it maytake longer time to call through the leads in the batch, and in turn,the predicted order of connection attempts (based on predictions scoredetermined prior to selecting the previous batch) may not be accurate(to yield optimal connection attempt outcomes) as time goes on when thelead records in the selected batch are getting processed to makeconnection attempts. To minimize the inaccuracy in the foregoingsituation, the batch size may be adjusted to an optimal size that mayprovide optimal results. For example, if a batch size is 50 and a batchof lead records selected at Monday: 9:00 is still being processed forconnection attempts at 9:18, as of 9:15 the order of the remaining leadrecords that are yet to be processed may not represent the optimal orderto yield optimal connection attempt outcomes; however, if the batch sizeis reduced to 15 and a batch of lead records selected at Monday: 9:00may be completely processed by 9:15, and the system may select a newbatch with optimal order at 9:15, which in turn may yield optimalconnection attempt outcomes. It should be noted that based onimplementation preferences, the Aggregation Time Interval used to derivethe derived connection attempt data and the batch size may be adjustedto optimal values to yield improved prediction accuracy and in turnyield optimal connection attempt outcomes.

In an embodiment of the System 70 (FIG. 1), for a given set of leads,the system may utilize one or more machine learning methods to predictone or more optimal time slots for executing connection attempts thatmay yield optimal results. For the given set of leads, the system may(i) determine the connect prediction score associated with each lead foreach time slot if connection attempts were to take place at that timeslot, and (ii) for each time slot determine a score (referred to hereinas the “time slot connect prediction score”) that predicts the number ofsuccessful connections that may occur in the time slot if thecommunication attempts were to take place at that time slot. Based onimplementation preferences, for each time slot, the time slot connectprediction score may be based on the connect prediction scores of theleads associated with that time slot. For example, the connectprediction scores of the leads may be added to arrive at the time slotconnect prediction score that may act as a representative score for thepredicted number of successful connections that may occur in that timeslot if the connection attempts were to take place at that time slot. Inthe foregoing embodiment, based on implementation preferences, theprediction of one or more optional time slots may be based on the timeslot connect prediction scores associated with various time slots.

In a variation of the foregoing embodiment involving phone call basedphone call based connection attempts and Scheduling App, for a given setof leads, the system may utilize a machine learning method todetermine/predict the time slot connect prediction score for each timeslot that may be available for a talker to execute communicationattempts (such time slot availability determined in the Scheduling App),wherein the availability of one or more dialing agents at various timesmay determine the availability of such time slots. Such time slotconnect prediction score associated with each available time slot mayrepresent the predicted number of phone calls answered if a dialingsession were to be executed at that time slot, and the system mayrecommend the time slots in the order based on the time slot connectprediction scores, optionally showing the time slot connect predictionscore for each time slot. The user may select the one or more of therecommended time slots and proceed to schedule the dialing session(s).It should be noted that a given set of leads may be associated with oneor more lead lists. Further, it should be noted that the time slot maybe defined based on implementation preferences, for example, the timeslot may be of duration 15 minutes, 30 minutes, 40 minutes, 60 minutes,3 hours, and the like.

In another embodiment of the System 70 (FIG. 1), the system may utilizeone or more machine learning methods to learn correlation amongmarketing analysis data (defined elsewhere in this document) and otherrelevant data associated with leads including, but not limited to, datastored in a customer relationship management system (CRM) and the like,and arrive at a score (referred to herein as the “sale predictionscore”) associated with each lead that represents the probability of thelead moving to a particular step in the sales process. Such particularstep in the sales process may be based on implementation preferences,including but is not limited to, the lead becoming not interested in aproduct, interested in seeing a demo of a product, interested in tryingto use a product on a trial basis, closing a sale of a product for apurchase of smaller volume or shorter duration usage, closing a sale ofa product for a purchase of larger volume or longer duration usage, andthe like. Further, based on implementation preferences, the system mayanalyze a given set of leads or leads in a given database (or anotherdata source) and order them based on certain criteria that definesoptimal outcomes (for example, probability of closing a sale in shortterm, by utilizing sale prediction score), and such ordering may allow asales rep/talker/texting rep to put effort towards those leads (such asmaking connection attempts to connect with those leads, via one or morephone call based and/or non-phone call based communication modes) thatmay yield optimal results, and which in turn may yield optimal results.A variation of the foregoing embodiment may utilize one or morefeatures/benefits of the System 70 (FIG. 1) and DCA to make connectionattempts. It should be noted that an embodiment of the System 70(FIG. 1) utilizing machine learning method for prediction thecommunication mode may be phone call based or non-phone call based (suchas text-based or other type of message based communication).

It should also be noted that when there is a reference to utilizing oneor more type of data (for example, lead data, connection attempt data,connection attempt outcome data, agent data, agent availability data,and the like) for analysis and/or learning correlation among theattributes of the data, based on implementation preferences, one or moreof the following may be applicable: (i) all or few groups of the saiddata may be utilized; (ii) for each group of data utilized, all orportion of the such group of data may be utilized, (iii) prior toutilizing a group of data, such group of data may be enriched with otherdata from one or more appropriate data sources, and (iv) specificweightage (referred to herein as the “weightage”) may be assigned forone or more group of data, to increase or decrease the importance if alead matches with a required pattern within such group of data, whengenerating a prediction score (such as sale prediction score, connectprediction score, time slot connect prediction score, or the like). Theforegoing term “group” refers to one or more attributes of a particulartype of data grouped together for learning patterns and correlation (forexample, patterns and correlation among leads, among connection attemptdata and connection attempt outcome data, and the like). It should benoted that the foregoing patterns and correlation learned may be used togenerate a prediction score for a lead (such as sale prediction score,connect prediction score, time slot connect prediction score, or thelike). It should also be noted that the term “data” may refer to aplurality of data, based on the context.

As a way of example, “Technology Data” may be a group that comprisesdata attributes associated with various technologies installed or usedby a lead or the business associated with the lead; “Intent Data” may bea group that comprises data attributes associated with intent of a leador other user(s) of the business associated with the lead to purchase aproduct or service; “Firmographic Data” may be a group that comprisesdata attributes/characteristics of the business associated with the lead(example, business size, revenue, age, location, ownership, growthstage, and the like) that may be used for segmenting a business;“Contactability Data” may be a group that comprises data attributesassociated with the ability to connect with a lead such as whether avalid phone number is available, whether a valid email address isavailable, whether the lead has been verified to be associated with aspecific business, whether the lead confirmed a preferred communicationmode to connect with, probability of connecting with the lead via acommunication mode at a given time, and the like.

FIG. 14 is an exemplary screen view illustrating an interface thatallows a user to assign weightage for data groups, in accordance with anembodiment of the system 70 (FIG. 1), wherein the system allows a userof the system to update/customize the weightage of one or more groups ofdata, wherein based on such weightage the system generates saleprediction score for a given lead.

As shown in FIG. 14, column 421 shows data group name; column 422 showsthe selected position in a sliding control as an indicator of weightageassigned to the data group in the same row; and column 423 shows thescore added when a lead matches with a required pattern within the datagroup located in the same row. Row 424 shows a slider with a positionset to near “Low” for the data group “Technology Data,” wherein if thelead matches with a required pattern within the Technology Data a scoreof 30 may be added by the system to the generated sale prediction score;row 425 shows a slider with a position set to near “Medium (in betweenLow and High)” for the data group “Firmographic Data,” wherein if thelead matches with a required pattern within the Firmographic Data ascore of 50 may be added by the system to the generated sale predictionscore; and row 426 shows a slider with position set to near “High” forthe data group “Intent Data,” wherein if the lead matches with arequired pattern within the Intent Data a score of 80 may be added bythe system to the generated sale prediction score. It should be notedthat in the foregoing example, if a lead matches the required patternsin all three data groups, the system may add 160 (30 plus 50 plus 80) tothe overall sale prediction score. The save button 427 allows the userto save the setting specified in the interface shown in FIG. 14. Itshould be noted that the term “required pattern” associated with aspecific data group, as referenced in the foregoing paragraph may bedefined by a user in the system.

Based on implementation preferences, a user may be allowed to set theposition in a slider control, but the score added associated with theslider control in the same row may be calculated automatically by thesystem based on the selected slider position. Based on implementationpreferences, the lowest and highest score to be added to the saleprediction score may be customized (for example, in the exemplaryinterface shown in FIG. 14, the lowest score to added may be 25 and thehighest score to be added may be 85 based on the left most and rightmost sliding control positions selected). Further, based onimplementation preferences, instead of providing a sliding control to auser, the interface may allow the user to directly input the score thatmay be added if a lead matches with a required pattern within a datagroup.

In an embodiment of the system 70 (FIG. 1) that utilizes sale predictionscore and connect prediction score to order leads for communicationattempts, based on implementation preferences, a specificpriority/importance/weightage may be given to one type of predictionscore in comparison to the priority/importance/weightage given to theother. For example, sale prediction score may be given higherpriority/importance/weightage than the connect prediction score, connectprediction score may be given higher priority/importance/weightage thanthe sale prediction score, both sale prediction score and connectprediction score are given equal priority/importance/weightage, or thelike. One having ordinary skill in the art would appreciate the varioustypes of prediction scores and various ways of assigningpriority/importance/weightage to one type of prediction score incomparison to the other type(s) of prediction score(s), based onimplementation preferences.

In yet another embodiment of the system 70 (FIG. 1), the system mayutilize one or more machine learning methods to learn correlation amongmarketing analysis data (defined elsewhere in this document) and otherrelevant data associated with leads including, but not limited to, datastored in a customer relationship management system (CRM) and the like,and for a given lead predict one or more of the following: (i) optimalcommunication mode to connect with the lead next, (ii) optimal time toexecute the next connection attempt, and (iii) optimal content/messagethat may yield optimal outcome during the next connection attempt.

Based on implementation preferences, the system may take into account(a) a variety of information associated with a lead including, but notlimited to, previous connection attempts, previous connection attemptexecution timings, previous connection attempt outcomes, and order ofdifferent connection attempts via different communication modes andtheir outcomes, and/or (b) any correlation learned from historicalactivities, which may include, but not limited to, touch specificoutcome correlation data (defined elsewhere in this document), marketingoutcome correlation data (defined elsewhere in this document), and orderof different connection attempts via different communication modes andoverall outcome (defined elsewhere in this document).

In an embodiment of the System 70 (FIG. 1), the system may learn thecorrelation among a variety of content/messages communicated with leadsand marketing analysis data (defined elsewhere in this document). Suchlearned correlation is referred to herein as the “message based outcomecorrelation data.” It should be noted that the marketing analysis datamay include outcome that is associated with actions such as a specificlink is clicked in an email delivered to a lead, downloading awhitepaper (or other electronic material) or placing an order using aspecific code sent in the email, opted out from further communication,and the like. For an example of such correlation, a message with aspecific content (“message 1”) may yield a higher connect rate withleads when the connection attempt using message 1 is executed at 9 am ona Tuesday, for a specific group of leads, and the touch is executed as a2^(nd) touch in the order of touches in the associated MTMC (definedelsewhere in this document). However, another message with a differentcontent (“message 2”) may yield a higher connect rate with leads whenthe connection attempt using message 2 is executed at 4 pm on a Friday(as the work week is about to wind down), for a specific group of leads,and the touch is executed as a 1^(st) touch in the order of touches inthe associated MTMC. Further, continuing the foregoing example, themessage2 may yield higher touch outcome than message1, however, message1may yield overall outcome that is of interest to the business (describedelsewhere in the document). One having ordinary skill in the art wouldappreciate that there may be numerous scenarios for coming up with otherexamples, associated with message based outcome correlation data.

It should be noted that the content/message may be communicated to alead may be via phone call based or non-phone call based communicationmode. For example, different content/messages communicated by an agentvia phone call may have an effect on the outcome.

The system may predict (or recommend or come up with) an appropriatecontent/message based on the time when a connection attempt is executed,to yield an optimal connection attempt outcome. It should be noted that,for an agent based touch, such a connection attempt execution time maydepend on agent availability, among other dependencies. For example,based on an execution time for an email based connection attempt, thesystem may come up with an effective email message that may yieldoptimal outcome (such as the lead responding back requesting to move toa next step in the sales process). Based on implementation preferences,such email message may be sent by the system automatically or after anagent reviews and confirms to send. For another example, based on anexecution time for a text based connection attempt (or in a specificstep within a text-based connection between an agent and the lead), thesystem may come up with an effective text message that may yield optimaloutcome (such as the lead agreeing to move to a next step in the salesprocess). For yet another example, based on an execution time for aphone call based connection attempt, the system may come up with aneffective script for the agent to use when communicating via phone call,that may yield optimal outcomes (such as the lead agreeing to move to anext step in the sales process).

One having ordinary skill in the art would appreciate that theScheduling App (described in the U.S. patent application Ser. No.14/204,505) may: (i) facilitate one or more talkers to be disciplined intime management by pre-scheduling and adhering to the pre-scheduledcommunication sessions. The foregoing benefit is similar to the benefitsassociated with pre-scheduling events in a calendar and managing timeeffectively, (ii) provide a feature that allows a user to schedule oneor more recurring events/communication sessions, and (iii) store andretrieve information in a database (or other mechanisms, including butnot limited to, a file system).

One having ordinary skill in the art would appreciate that based onimplementation preferences, the central communication server 150(FIG. 1) of the system 70 (FIG. 1) may be located at the location of atalker or closer to geographical location of the talker, which mayeliminate the phone communication costs associated with long distancephone connectivity between the talker's phone and the centralcommunication server 150 (FIG. 1). Further, the central communicationserver 150 (FIG. 1) may be owned and/or hosted by the businessassociated with the talker, in which case the Vendor (described in theU.S. patent application Ser. No. 14/204,505) may not incur costsassociated with hosting the central communication server 150 (FIG. 1)and any associated phone communication costs. The foregoingimplementation preferences may provide flexibility in business modelchoices for the Vendor due to reduction in operating costs.

It should be noted that based on implementation preferences, if theSystem 70 (FIG. 1) uses non-phone call based communication, thecomponent of the system that enables connectivity between an agent and alead (i) may be located at the location of the agent or closer togeographical location of the agent, and/or (ii) may be owned and/orhosted by the business associated with the agent, to provide flexibilityand reduce costs associated with communication. For example, in the caseof text-based communication, the text-based connectivity between atexting rep and a lead may be established by the central communicationserver 150 (FIG. 1) that is located at the business associated with thetexting rep, wherein the central communication server 150 (FIG. 1) hastext-based communication capability. In the foregoing example, if thetexting agent is present (that is, the texting agent functionality isnot fully automated), based on implementation preferences the text-basedcommunication between the texting agent and the lead may be establishedby the central communication server 150 (FIG. 1).

One having ordinary skill in the art would appreciate that the system 10(FIG. 1) disclosed in the U.S. patent application Ser. No. 13/278,764may be modified to allow a talker (or another authorized user) to createone or more campaigns, wherein each campaign may have one or moreattributes with values specific to that campaign, and the value for oneor more attributes may be optional. Based on implementation preferences,a campaign attribute may include but is not limited to, one or more ofthe following fields/attributes: campaign identifier, campaign name,campaign start time, campaign end time, a field to identify one or moretalkers, a field to identify one or more dialing agents, a field toidentify one or more customers for attempting to connect with, and thelike.

One having ordinary skill in the art would appreciate that based onimplementation preferences and ease of use, the system 10 (FIG. 1)disclosed in the U.S. patent application Ser. No. 13/278,764 may beimplemented to do one or more of the following: (i) one or more talkersmay be assigned to be part of a list referred to herein as the “talkerlist,” (ii) one or more dialing agents may be assigned to be part of alist referred to herein as the “dialing agent list,” (iii) a talker maybe assigned to be part of one or more talker lists, (iv) a dialing agentmay be assigned to one or more dialing agent lists, (v) whencreating/updating a campaign, one or more dialing agents may bespecified by selecting one or more dialing agent lists, (vi) whencreating/updating a campaign, one or more talkers may be specified byselecting one or more talker lists, and (vii) when creating/updating acampaign, one or more customers may be specified by selecting one ormore customer lists.

The term “personal characteristics” refers to one or morecharacteristics associated with a person, including but not limited to,linguistics characteristics, language skill, management skill, technicalskill, product skill, certification in certain skill, geographicallocation, cost, and the like. One or more dialing agents may be assignedto be part of a dialing agent list based on personal characteristics ofthe one or more dialing agents. One or more talkers may be assigned tobe part of a talker list based on personal characteristics associatedwith the one or more talkers. One or more customers may be assigned tobe part of a customer list based on one or more characteristicsassociated with the one or more customers, wherein the characteristicsof a customer may include but is not limited to, language, knowledge ofcertain products, geographical region, personal characteristicsassociated with the customer, and the like.

Further, one having ordinary skill in the art would appreciate that thesystem 10 (FIG. 1) disclosed in the U.S. patent application Ser. No.13/278,764 may be implemented to do one or more of the following: (i)maintain the relationship between a customer list and one or more talkerlists compatible/allowed to be associated with the customer list, (ii)maintain the relationship between a customer list and one or moredialing agent lists compatible/allowed to be associated with thecustomer list, and (iii) upon the user (who is creating or updating acampaign) selecting/specifying a customer list as part of the campaign,automatically prefill or aid to prefill one or more talkers (or talkerlists) and/or one or more dialing agents (or dialing agent lists)compatible/allowed to be associated with the customer list.

One having ordinary skill in the art would appreciate that there may bea many-to-many relationship between customer lists and dialing agentlists, wherein the relationship between a customer list and a dialingagent list may be based on the compatibility between the personalcharacteristics of the dialing agents and the requirement to achievereasonably effective communication with the customers associated withthe customer list. Further, there may be a many-to-many relationshipbetween customer lists and talker lists, wherein the relationshipbetween a customer list and a talker list may be based on thecompatibility between the personal characteristics of the talkers andthe requirements to effectively communicate with the customersassociated with the customers list.

The Telephone Consumer Protection Act (TCPA) is a federal law with newrules which took effect on Oct. 16, 2013 that prohibit companies fromcontacting consumers with automated phone calls or text messages totheir mobile/wireless phone numbers without their prior consent. It is aviolation of this rule if a business autodials a mobile number or sendsa text to a mobile number using an automated system without having aprior written consent from the current owner of that mobile number tocommunicate using such automated telephone technology. The challengesare: (i) phone numbers are easily migrated from landline to mobile andvice versa with a quick turn-around time for such migration, and (ii) aphone number may be migrated from one owner to another owner easily anda large number of phone numbers are recycled/reassigned to new owners.For example, a business may have confirmed that a particular phonenumber is a landline a few days ago, but as of today that phone numbermay no longer be a landline, and instead it may have been migrated to amobile phone number. For another example, a business may have obtained aprior written consent a few days ago from the owner of a mobile phonenumber for contacting using an automated system, but as of today theremay be a new owner to that mobile phone number and the previouslyobtained consent may no longer be valid. Violation of TCPA may end upresulting in costly legal bills and penalties.

Hence, it is desirable to have a module in the System 70 (FIG. 1) thatautomates the verification of one or more of the following: (i) whethera phone number associated with a customer is a mobile phone number or alandline phone number, (ii) whether the customer is the currentowner/subscriber of the phone number, and/or (iii) whether the businessusing the System 70 (FIG. 1) has obtained a prior written consent fromthe current owner of the phone number. Such module is referred to hereinas the “TCPA compliance module.” One having ordinary skill in the artwould appreciate that the TCPA compliance module may help one or morebusinesses and/or users using the System 70 (FIG. 1) to be compliantwith TCPA and other relevant laws, rules, and regulations. Besidesoffering the benefit of compliance with TCPA rules, by improving theaccuracy of the data (including but not limited to, phone type andcurrent owner) the TCPA compliance module may further help thebusinesses and users of the System 70 (FIG. 1) to dramatically improveconnect rates (number of connection attempts that result in connectingwith the customer or lead) as well as operational efficiencies byallowing them to reach the right customers with the right message. Itshould be noted that based on implementation preferences the System 70(FIG. 1) may not fall under the automated dialing technology.

In an embodiment of the System 70 (FIG. 1) having a TCPA compliancemodule, based on implementation preferences, the customer records/leadrecords that do not comply with the TCPA rules may be distinguished invariety of ways, including but not limited to, highlighting differently,blinking, shading, being shown in a specific area of the screen, beingshown in a separate computer screen, not showing such records byfiltering them out, and the like. It should be noted that one or morefeatures/benefits of the TCPA compliance module may be implemented as astand-alone system or as a module as part of an embodiment of the System70 (FIG. 1).

The TCPA compliance module may utilize consistent up-to-date phone data(“customer phone data”) that enables verification of whether a givenphone number is a mobile (wireless) or landline (wireline) phone, andfurther allows verification of whether a given customer name and phonenumber go together or whether the phone number now belongs to adifferent person. If a given phone number and a given customer name areverified go together, then the user of the system can be confident thatthey are contacting the right person. It should be noted that thecustomer phone data may be provided by one or more third parties.Instead of using the customer phone data provided by third partycompanies, one may choose to build a database with the phone type andphone ownership associated with each phone number and keep such adatabase up-to-date by gathering changes to the data from varioussources (including, but not limited to, different phone companies),however, building/maintaining such a database may be cumbersome.Further, the TCPA compliance module may utilize up-to-date customerconsent data (“customer consent data”) that maintains a record ofconsent provided by a customer along with relevant data that may includebut not limited to, customer name, whether consent was obtained, timewhen consent was obtained, and the like, and the TCPA compliance modulemay distinguish the phone numbers that should not be contacted using anautomated system.

FIG. 15 is an exemplary screen view illustrating an interface thatallows a user to enable TCPA compliance feature, in accordance with anembodiment of TCPA compliance module. As shown by FIG. 15, a user mayenable the TCPA compliance feature by selecting (checking off) acheckbox 642. The user may click a save button 644 to save the updatedsettings in the interface. Upon saving the value associated with theselected checkbox 642 the system enables the functionality of the TCPAcompliance module.

FIG. 16 is a flowchart illustrating actions performed when processing agiven customer name and a given phone number associated with thecustomer name to validate whether the phone number is a mobile phonenumber and if it is a mobile phone number whether consent is receivedfrom the current owner of the phone number, in accordance with anembodiment of TCPA compliance module. As shown by block 662, the systemchecks whether the given phone number is a mobile phone number, byverifying the phone number against the customer phone data. If thesystem determines that the given phone number is not a mobile phonenumber in block 662 then the system proceeds to make the phone call tothe phone number, without further verification (since TCPA compliancefunctionality is relevant only if the phone number is a mobile phonenumber), as shown by block 668. However, if the system determines thatthe phone number is a mobile phone number in block 662 then the systemproceeds to further check whether the given owner name associated withthe given phone number (in this case, mobile phone number) matches withthe current owner name associated with the said mobile phone number, asshown by block 664, by verifying whether the given customer name matcheswith the current customer name associated with the said mobile phonenumber. If the system determines that the given customer name does notmatch with the current owner name associated with the said mobile numberin block 664, the system does not make the call to the given number, asshown by block 670. However, if the system determines that the givencustomer name matches with the current owner name associated with thesaid mobile number in block 664, then the system further checks whetherthere is a consent obtained from the customer associated with the givencustomer name (in this case, same as the current customer of the saidmobile number), as shown by block 666. If the system determines thatthere is no consent obtained from the given customer in block 666, thesystem does not make a call to the given phone number, as shown by block670. However, if the system determines that there is a consent obtainedfrom the given customer in block 666, the system proceeds to make a callto the given phone number, as shown by block 668.

There may be other laws similar to TCPA that may prohibit one to contacta customer via phone call (or non-phone call) based communication mode.One having ordinary skill in the art would appreciate that a module maybe implemented using a variant of one or more of the techniques taughtin the foregoing description of the TCPA compliance module.

As described in the U.S. patent application Ser. No. 13/278,764 and inthis document, the selection of customer records associated with adialing session and/or the selection of a customer for calling next maybe dynamically decided by the system 70 (FIG. 1) based on variety offactors, including but not limited to, priority information associatedwith a customer, a new update made to one or more attributes of acustomer record, a calendar event scheduled for follow-up with acustomer, one or more customer records newly becoming available (such anewly available customer record is referred to herein as the “newcustomer record”) that meet the criteria to be part of the list ofcustomers associated with the dialing session, and the like. Further, inaccordance with the foregoing system, such dynamically selected customerrecords may be selected as a batch of one or more customer records andtransmitted to be available in one or more talker computers and/or oneor more dialing agent computers, wherein the list of customer records(and associated customer data) shown on the one or more dialing agentcomputers may or may not be the same as that shown in the one or moretalker computers, at any given time. Also, in an embodiment of thesystem 70 (FIG. 1), the function of a dialing agent and a dialing agentcomputer may be automated by one or more modules located in one or moreof the following: central data server 100 (FIG. 1), centralcommunication server 150 (FIG. 1), and talker computer 24 (FIG. 1),wherein the dialing agent and the dialing agent computer may not bepresent, and in such embodiment, a talker may be referred moreappropriately as an agent and the taker computer may be referred moreappropriately as the agent computer.

One having ordinary skill in the art would appreciate that the criteriato select a batch of one or more records associated with a dialingsession may include a criterion that selects one or more customerrecords newly becoming available. Such new customer records may becomeavailable automatically based on the customer information submitted byone or more customers through variety of methods (for example, via a webform, phone call, email, text message, and the like) or the informationrelated to one or more new customers may be gathered and the associatedone or more new customer records may be created/entered/made availableby a user of the system (or a user of another system).

Further, based on implementation preferences in an embodiment of theSystem 70 (FIG. 1) utilizing phone call based communication mode, one ormore of the following may happen: (i) the one or more new customerrecords may not be made available in the System 70 (FIG. 1) and insteadmay be made available in a data source other than the System 70 (FIG.1), and in that case, the System 70 (FIG. 1) may obtain the new customerrecords via data synchronization and make the one or more customerrecords available as a batch of one or more customer records to thedialing session, and (ii) the one or more new customer records may beassigned a specific priority and the system may select the one or morenew customer records for calling next, at a time including but notlimited to, immediately after the one or more new customer recordsbecame available, after a specific amount of delay (based onimplementation preferences), or after receiving an acknowledgement froma talker (or another user of the system) to select the one or more newcustomer records for calling, based on the position of a new customerrecord within the order of the customer records, and the like. Onehaving ordinary skill in art would appreciate that in the case when thetalker (or user) is required to provide the foregoing acknowledgement,the talker (or user) may have the option to start calling a new customer(associated with a new customer record) immediately after completing thethen currently on-going call, after suspending/dropping the thencurrently on-going call or the like. One having ordinary skill in theart would appreciate that based on implementation preferences, if adialing agent is present in the foregoing embodiment (that is, thedialing agent function is not automated), when calling a new customerassociated with a new customer record, such call attempt may be made byan available dialing agent, or such call attempt may be made by atalker. If the dialing agent is not present in the foregoing embodiment,the call attempt (referred in the foregoing sentence) may be made by thetalker. One having ordinary skill in the art would appreciate that in anembodiment of the System 70 (FIG. 1) having no dialing agentpresent/participating, the dialing agent function may be fully automatedor partially automated or no part of dialing agent function is automated(and any portion of the dialing agent function that is not automated maybe performed by a talker). Further, the order of the customer records(including but not limited to the one or more new customer records) forcommunication attempts, at any given time, may be based on variety offactors including but not limited to, prioritization information, orderpredicted by one or more computer learning methods (described elsewherein this document), and the like. One having ordinary skill in the artwould appreciate that based on implementation preferences, when a newcustomer record becomes available, such new customer record may bestored/shown/processed in variety of ways, including but not limited to,the new customer record may be inserted at an appropriate positionwithin a set of customer records previously available in a talkercomputer, appended along with the previously delivered customer recordsand sorted, or the like. Further, based on implementation preferences, anew customer record may be stored/shown/processed in a dialing agentcomputer in a variety of ways similar to the talker computer. Based onthe context, the reference to a singular new customer record may mean torefer plurality of new customer records.

Further, based on implementation preferences, in a system that processesnew customer records in accordance with the present invention, an agentcomputer (or a talker computer or a dialing agent computer or usercomputer) may show the one or more new customer records in a variety ofways, including but not limited to, display in the same area of thescreen where customer records associated with incoming phone calls(described below) are shown (that is, mixed with the customer recordsassociated with incoming phone calls or shown separately), display inthe same area of the screen where other customer records are shown (thatis, mixed with other customer records or shown separately), display inone or more separate areas of the screen (or in one or more separatescreens, if applicable), distinguishing the new customer recordsdifferently from other customer records, and the like. It should benoted that one or more new customer records associated with a newcustomer that is currently connected with an agent may be distinguishedfrom the other customer records in yet another way. Also, based onimplementation preferences, the System 70 (FIG. 1) may utilize one ormore communication modes that may be Real Time Based Communication based(for example, phone call) or Non Real Time Based Communication based(for example, text message, email, or the like).

Based on implementation preferences, the functionality described forprocessing one or more new customer records may be applicable to processa customer record that becomes ready for a communication attempt,wherein such customer record becomes ready based on: (i) a previouslyscheduled calendar event for follow-up with the customer associated withthe customer record, and/or (ii) selection of such customer record tomake a connection attempt by a computer learning method that analyzesand learns correlation among lead data (defined elsewhere in thisdocument) and/or marketing analysis data (defined elsewhere in thisdocument).

FIG. 17 is a flowchart illustrating actions performed when a customerrecord is selected for connection attempt, in accordance with anembodiment of system 70 (FIG. 1) that processes new customer records. Asshown by block 682, the system checks whether there is a new customeravailable. If there is a new customer available, the system delivers thenew customer record to an agent computer, as shown by block 684. In theforegoing step, based on implementation preferences, instead ofdelivering the customer record the system may deliver a uniqueidentifier (stored in one or more fields/attributes of the customerrecord) associated with the customer record to the agent computer, whichmay be used by the agent computer to identify/retrieve the customerrecord. As shown by block 686, upon receiving the customer record (or anassociated unique identifier) the agent computer identifies the customerrecord and distinguishes differently, for the purpose of an agentassociated with the agent computer to recognize the new customerrecord(s) differently from other customer records. As shown by block688, upon the agent acknowledge to start the connection attempt toconnect with the new customer, the system starts the said connectionattempt. It should be noted that based on implementation preferences,the foregoing connection attempt may be phone call based or non-phonecall based communication modes such as text based communication mode.

FIG. 18 is an exemplary screen view illustrating an interface showingnew customer records, in accordance with an embodiment of system 70(FIG. 1) that processes new customer records. As shown by FIG. 18, rows702, 704, and 706 show three new customer records shown in the topsection of the tabular view, which are denoted by the symbol “N” in thefirst column to indicate that they are new customer records. Row 702 isshaded with a lighter shade to indicate that a connection attempt isbeing made currently (or a connection attempt is scheduled to be madenext) to connect with a customer associated with row 702. When needed,the agent may click the stop connection attempt button in the row 702 toend the connection attempt. Based on implementation preferences, theforegoing connection attempt may be phone call based or non-phone callbased communication modes such as text based communication mode. Theagent may click the start connection attempt button in the row 704 toinitiate connection attempt to the customer associated with row 704.Based on implementation preferences, upon initiating a new connectionattempt, if there is any other connection attempt is also active thesystem may end that active connection attempt such active connectionattempt may be ended. As shown by FIG. 18, section 708 shows othercustomer records (other than the new customer records) associated withthe communication session (for example, for outbound calling). It shouldbe noted that based on implementation preferences, instead of showingthe new customer records in the top section of the tabular view, the newcustomer records may be mixed/shown with the other customer recordsshown at the bottom of the tabular view.

One having ordinary skill in the art would appreciate that in anembodiment of the System 70 (FIG. 1) utilizing phone call basedcommunication mode when there is an incoming phone call originated froma customer (or lead) the central communication server associated withthe System 70 (FIG. 1) may be configured to recognize such incomingphone call and route the phone call appropriately. Such routing may bebased on one or more attributes associated with the incoming phone calland other relevant attributes such as the time when the phone call isreceived. One having ordinary skill in the art would appreciate that theattributes of a phone call may include, but are not limited to, callingparty information, called party information, and the like. Further,called party information may include Caller ID information whichtypically comprises of the caller's telephone number (CNUM) and caller'sname (CNAME). That is, CNUM refers to the telephone number of thecalling party on an inbound call, CNAM refers to the name associatedwith the CNUM of the calling party on an inbound call. Based onimplementation preferences, and CNUM and/or CNAM may be presented whenan inbound call is received. For an example of routing a phone call, ifa phone call has a calling party phone number/CNUM starting with areacode 781 it may be routed to a queue called “MA Customers.” For anotherexample, if a phone call is received after 5 pm EST the phone call maybe routed to a queue called “After Working Hours.”

In a conventional system that handles incoming phone calls, when thereis integration between the phone system and an agent computer, afterrecognizing the called party phone number and/or name the system mayautomatically show a window on the agent computer, displayinginformation associated with a phone call concurrently sent to thatagent's telephone (such window is referred to herein as the “screenpop”). The information associated with a phone call is referred toherein as the “screen pop information,” which may be based on one ormore attributes associated with the incoming phone call and otherrelevant attributes such as the time when the phone call is received.For example, the screen pop information may include the caller's firstname, last name, title, company name, historical activity notes, and thelike. Screen pop information may be obtained from one or more datasources including but not limited to CRM, customer service system, andthe like, that may have information associated with phone call.

In a conventional system handling incoming phone calls, one or morephone calls may be routed to a queue where the callers may be waitingand then assigned to an agent upon the agent becoming available. When aphone call from a queue is assigned to an agent, the system may start toobtain the screen pop information (associated with that phone call), andbased on the volume of data that may be searched to locate the screenpop information, the speed associated with obtaining and presenting thescreen pop information may be significantly slow, and in turn the agentmay not be able to see important information associated with the callerin a timely manner. An embodiment of the System 70 (FIG. 1) may overcomethe foregoing limitation by doing the following: (i) start searching(and/or fetching) for the screen pop information associated with a phonecall upon the incoming phone call being assigned to a queue (which maybe ahead of the agent answering the call) and keep the screen popinformation ready to be delivered to an agent's computer, and (ii) uponan agent becoming available and the incoming phone call isassigned/bridged/transferred to the agent's phone connection,concurrently transmit/deliver the screen pop information to the agent'scomputer. The foregoing functionality of the System 70 (FIG. 1) isreferred to herein as the “screen pop fetch ahead functionality.” Basedon implementation preferences, the system may start searching for screenpop information upon receiving the incoming phone call (even prior torouting the call to a queue).

Further, in a conventional system handling incoming phone callsconfigured to route incoming phone calls (including any call that istransferred) to a queue, the following limitations exist: (i) an agentmay not be able to review activity notes history and other relevantinformation associated with a customer waiting in a queue, ahead of thecustomer call is assigned/bridged/transferred to the agent, and (ii) theincoming phone calls waiting in the queue may be answered typically inthe order the phone calls are received, and an agent (or another user)may not be able to review relevant information associated with customerswaiting the queue and update the order of answering the phone calls. Anembodiment of the System 70 (FIG. 1) may address/overcome the foregoinglimitations by showing relevant information associated with a customerwaiting in a queue to the agent associated with the queue, prior to thephone call assigned/bridged/transferred to the agent's phone connection,which may enable the agent to do one or more of the following: (i) beprepared by reviewing activity notes history and other relevantinformation associated with the customer, ahead of the customer call istransferred, and (ii) change the order in which one or more customerswaiting in the queue may be answered, by updating the queue, updatingone or more attributes associated with the customers waiting in thequeue, or selecting a particular customer waiting in the queue andanswering that customer's call, or the like. The foregoing functionalityof the System 70 (FIG. 1) is referred to herein as the “queue visibilityfunctionality.” Based on implementation preferences, the foregoingembodiment may or may not have the screen pop fetch ahead functionalityincluded. Further, the relevant information associated with a customermay or may not include all or partial of screen pop information.

In an embodiment of the queue visibility functionality, the system mayenable a computer used by an agent (associated with a queue where thecustomers associated with incoming calls or transferred calls arewaiting) to distinguish one or more customer records associated with thecustomer whose call is currently assigned/bridged/transferred to theagent's phone connection, differently from the other customer records.Based on implementation preferences distinguishing (referenced in theforegoing sentence) may be accomplished in a variety of ways, includingbut not limited to, highlighting in a particular way.

In an embodiment of the queue visibility functionality, the system mayemploy a computer learning method that utilizes all or portion of thedata from a group that comprises of marketing analysis data, marketingoutcome correlation data and touch specific outcome correlation data, toorder the customers waiting in a queue.

One having ordinary skill in the art would appreciate that there may bemore than one agent and more than one queue in a system that handlesincoming phone calls. Further, an agent may be assigned/mapped to morethan one queue, and more than one agent may be assigned/mapped to aqueue. One or more criteria that define the mapping between one or moreagents and one or more queues may be based on queue characteristics andagent characteristics. Examples of queue characteristics may include,but are not limited to, an initial greeting to be played to the caller,wait time beyond which the call of the caller may be forwarded (forexample, to another phone number, queue, and the like), failoverforwarding number for re-routing based on certain criteria, and thelike. When an agent is assigned to more than one queue, customer phonecalls routed to any one of those queues may be assigned to the agent.

Further, based on implementation preferences, in a system that processesincoming phone calls in accordance with the present invention, an agentcomputer (or talker computer or a dialing agent computer or usercomputer) may show the one or more customer records associated withcalls waiting in a queue in a variety of ways, including but not limitedto, displaying in the same area of the screen where new customer records(described above) are shown (that is, mixed with the new customerrecords or shown separately), displaying in the same area of the screenwhere other customer records are shown (that is, mixed with othercustomer records or shown separately), showing in one or more separateareas of the screen (or in one or more separate screens, if applicable),distinguishing the associated customer records differently from othercustomer records, and the like. It should be noted that one or more newcustomer records associated with an incoming phone that is currentlyconnected with an agent may be distinguished from the other customerrecords in yet another way. Also, based on implementation preferences,in addition to or instead of incoming phone calls, the System 70(FIG. 1) having the screen pop fetch ahead functionality and/or queuevisibility functionality, may utilize such functionality to handlecommunication originated from one or more customers via one or more RealTime Based Communication and Non Real Time Based Communication modesthat may not be phone call based (for example, text message, or thelike).

FIG. 19 is a flowchart illustrating actions performed to fetch screenpop information and deliver necessary portion of the screen popinformation to an agent computer when a new incoming call arrives to aqueue, in accordance an embodiment of the system 70 (FIG. 1) thatprocesses incoming phone calls and have queue visibility functionality.As shown by block 722, the system checks whether there is any newincoming call arrive to an incoming call queue. If there is an incomingcall arrive to the incoming queue (block 722), the system proceeds tofetch screen pop information associated with the incoming call, as shownin block 724. Based on implementation preferences, the system may usecalling party's caller id associated with the incoming call and look upleads or contacts or accounts stored in CRM and fetch the screen popinformation. Upon screen pop information is fetched, the system deliversall or necessary portion of the screen pop information to the agentcomputer, as shown in block 726. In the agent computer, such deliveredportion of the screen pop information may be shown as a customer recordassociated with the incoming call. Based on implementation preferences,prior to screen pop information is fetched, the system may deliverlimited amount of information associated with the incoming call (suchas, calling party's caller id).

FIG. 20 is a flowchart illustrating actions performed when transferringa an incoming call waiting in a queue, to an available agent thatanswers the incoming call, in accordance with an embodiment of system 70(FIG. 1) that processes incoming phone calls and have queue visibilityfunctionality. As shown by block 742, the system checks whether an agentanswered an incoming call. If the agent answered the incoming call, asshown by block 744 the system transfers the incoming call from the queue(where the incoming call is waiting) to the agent's phone, and also sendnotification to an agent computer associated with the agent that enablesthe agent computer identify the customer record(s) associated with thetransferred incoming call. Based on implementation preferences, suchtransfer may be performed by transferring the incoming call to aconference bridge the agent's phone may be connected to (that is, theconference bridge where the agent is waiting). Upon receiving theforegoing notification, the agent computer distinguishes one or morecustomer records associated with the transferred incoming call, as shownby block 746.

FIG. 21 is an exemplary screen view illustrating an interface showingcustomer records associated with incoming calls waiting in one or morequeues, in accordance with an embodiment of system 70 (FIG. 1) thatprocesses incoming calls and have queue visibility functionality. Asshown by FIG. 21, rows 762, 764, and 766 show three customer recordsassociated with incoming calls shown in the top section of the tabularview, which are denoted by the symbol “IC” in the first column toindicate that they are customer records associated with incoming calls.It should be noted that a customer record (associated with an incomingcall) may have attributes populated from the screen pop informationassociated with the incoming phone call. Row 762 is shaded with alighter shade to indicate that the customer record of row 762 isassociated with an incoming phone call transferred to the agent's phone.Based on implementation preferences, such transfer may be performed bytransferring the incoming call to a conference bridge the agent's phonemay be connected to (that is, the conference bridge where the agent iswaiting). When needed, the agent may click the end the call button inthe row 762 to end the transferred incoming call. The agent may clickthe answer the call button in the row 764 to answer (or request toconnect with) the incoming call associated with the customer record of764. Based on implementation preferences, upon answering an incomingcall, if there is any other phone call is active the system may end suchactive phone call and proceeds to answer the said incoming call. Asshown by FIG. 21, section 768 shows new customer records for connectionattempts using a communication mode (for example, via phone call or textbased communication), which are denoted by the symbol “N” in the firstcolumn to indicate that they are new customer records.

In FIG. 21, section 770 shows other customer records (other thancustomer records associated with incoming phone call and the newcustomer records) associated with the communication session (forexample, for outbound calling). It should be noted that based onimplementation preferences, instead of showing the customer recordsassociated with the incoming phone calls in the top section of thetabular view, the said customer records may be (i) mixed/shown with thenew customer records in the middle section of the tabular view shown inFIG. 21, or (ii) mixed/shown with the other customer records shown atthe bottom section of the tabular view shown in FIG. 21. Based onimplementation preferences, all three types of leads records (customerrecords associated with incoming phone calls, customer recordsassociated with new customers, other customer records) may bemixed/shown in one section of the tabular view shown in FIG. 21.

It should be noted that a system that embodies the functionality tohandle incoming phone calls described herein, if more than one agent isassociated with a queue, when an incoming phone call associated with thequeue is ready to be presented to an agent for handling, one or moreavailable agents may be selected using various strategies such as roundrobin, ring all, least busy agent, and the like. One of ordinary skillin the art will appreciate that other forms of selection of agents notdisclosed herein that are familiar to those of ordinary skill in the artmay be utilized by the foregoing system.

Based on implementation preferences, an agent (or user) in an embodimentof the System 70 (FIG. 1) may create and keep updating one or more listsof customers by associating/disassociating one or more customers withthe list, and may use such list for attempting to connect with one ormore customers. Such creation and updating of the list is referred toherein as the “List Management.” For the purposes of understanding, astatic list is a list wherein the one or more customers associated withthe list may not change unless a user of the system manuallyadds/deletes one or more customers to/from the list, however, a dynamiclist is a list wherein the one or more customer associated with the listmay be identified automatically based on the criteria specified for thedynamic list and thereby the system may dynamicallyassociate/disassociate the one or more customers associated with thedynamic list based on the criteria specified.

For the purposes of definition, a “Rule Triggering Event” means anyactivity/event taking place in the System 70 (FIG. 1) that may be usedas a trigger to initiate execution of one or more Rules Actions (definedbelow). A “Rule Action” means any activity/event/action taking place inthe System 70 (FIG. 1), including but is not limited to, creation,deletion, or updating of one or more fields and/or records in the System70 (FIG. 1) and/or one or more third party systems, generating a report,sending an email, sending a text, or the like. Based on implementationpreferences, one or more Rule Triggering Events and one or more RuleActions are associated with a workflow profile/rule (referred to hereinas the “workflow rule”). Further, one or more authorized users of theSystem 70 (FIG. 1) may be given access to create/update/delete aworkflow rule.

The creation and maintenance of static list (via updating) may belaborious, time consuming, and error-prone due to the manual nature ofthe process involved in adding/deleting one or more customers to/fromthe list and/or updating attributes of membership of a customer in alist. For example, certain CRM systems may allow creation of a campaign,associating one or more customers to that campaign, and updatingmembership attributes associated with each customer's membership in thecampaign. Further, in the case of a dynamic list, though theaddition/deletion of one more customer to/from the dynamic list may beautomated by the system based on criteria specified, keeping the dynamiclist updated may be time consuming and error-prone because the specificcriteria used by the system to associate/disassociate one or morecustomers with the list may depend on manual update to one or moreattributes associated with the customer, wherein the update may beerror-prone.

Further, during a communication session, there may be significantupdates taking place in the System 70 (FIG. 1) that may need to bepropagated to appropriate data structures/attributes stored within theSystem 70 (FIG. 1) as well as other third party systems, for thepurposes of performing tasks associated with List Management. Suchupdates may include, but are not limited to, the outcome of a connectionwith a customer (such an outcome of the connection referred to herein asthe “connect disposition”), updates to fields associated with one ormore customer records, and the like. It should be noted that the updatestaking place in the System 70 (FIG. 1) may be initiated by a user (or amodule within the system). Example values of a connect dispositioninclude, but are not limited to, “Meeting scheduled,” “Ready to receiveproposal,” “Call back in 30 days,” “Call back in the future,” “Notinterested,” “Not a right contact,” “No longer works there,” “Reachedvoice message,” “Wrong phone number,” or the like.

As a way of example, in an embodiment of the System 70 (FIG. 1)utilizing a phone call based communication mode, a talker may conduct adialing session to reach customers in a list called “Active prospects tocall.” Upon completing a connect/phone call with a customer in theActive prospect to Call list, the talker may enter “Call back in thefuture” as the connect disposition. Then, the talker may manuallyperform the following List Management tasks: (i) remove/disassociate thecustomer from the list “Active prospect to call,” and (ii) associate/addthe customer to a list called “Keep in touch once in 90 days” for thepurposes of communication attempt to the customer once in 90 days. Inthe foregoing example, instead of moving the customer from one list toanother manually, the talker may update a field associated with thecustomer called “Follow-up category” with a value “Once in 90 days” andupon such update the customer may be disassociated and moved from thelist “Active prospects to call” to “Keep in touch once in 90 days” (ifboth of those lists are configured as dynamic list with criteria thatenables such automatic disassociation of the customer from the firstlist and association with second list). It should be noted that in theforegoing example, the talker may perform the one or more ListManagement tasks in the System 70 (FIG. 1) and/or one or more externalsystems.

The tasks associated with the List Management are laborious, timeconsuming, and error-prone if performed manually or in a semi-automatedprocess. Hence, it is desirable to have a workflow module (referred toherein as the “Workflow Module”) that provides one or more of thefollowing functionality: (i) allow one or more users of the system todefine/configure one or more rule that upon one or more occurrences ofone or more Rule Triggering Events, may cause the execution of one ormore Rule Actions, (ii) automatically associate or disassociate one ormore customers to/from one or more lists upon the criteria for suchassociation or disassociation is met, (iii) allow one or more users ofthe system to define/configure data access criteria that includes, butis not limited to, settings information that specifies which user mayaccess a field and whether the user may have read-only access orread-write access or read-write-delete access to one or more fieldsand/or records, and (iv) the like. It should be noted that the word“associate” as in “associate the customer to the list” may mean “add” or“attach” or “link,” and the word “disassociate” as in “disassociate thecustomer from the list” may mean “remove” or “detach” or “separate.” Itshould be noted again that based on the context the word “customer” mayrefer to the “one or more customer record” associated with the customer.Further, the word “update” as in “update a field” or “update a record”means create or update or delete a field/record.

By way of an example, in an embodiment of the System 70 (FIG. 1)utilizing phone call based communication mode, a user of the WorkflowModule may specify that a dialing agent can have read-only access to thefields account name, contact first name, and contact last nameassociated with a customer record, however, the dialing agent may haveread-write access to title and phone number fields that allows thedialing agent to update those fields if necessary, and the dialing agentmay not have access to the field “purchase history” that has sensitivepurchase history information that the dialing agent does not have a needto know.

It should be noted that any update taking place in accordance to theWorkflow Module, may take place in System 70 (FIG. 1), or take place inone or more external systems, or any combination thereof. Further, thenature of such an update and the number of attributes/fields gettingupdated may not be identical across each system. One having ordinaryskill in the art would appreciate that there may be more than one userof the system using the Workflow Module concurrently, and also there maybe more than one activity/event in the Workflow Module happeningconcurrently which may result in more than one update taking placeconcurrently.

Further, it should be noted that if a Rule Action involves updates to athird party system, the system may have configuration settings thatspecify when to update, what data to update, and how to update the thirdparty system. There may be connectivity between the System 70 (FIG. 1)and a third party system (from which customer records are uploaded,wherein updates may be sent to the third party system to update thecustomer records that were uploaded) that enables synchronization ofappropriate data in both systems. One having ordinary skill in the artwould appreciate various techniques that may be used to accomplish suchsynchronization including, but are not limited to, having a module inthe System 70 (FIG. 1) to push or pull the data to/from the third partysystem, having a module in the third party system to pull or push thedata from the System 70 (FIG. 1), having a separate system thatsynchronizes the data between the System 70 (FIG. 1) and the third partysystem, or the like.

It should be noted that based on implementation preferences, when theSystem 70 (FIG. 1) is trying to access a third party system forsynchronization and if the third party system is not responding in atimely manner, the System 70 (FIG. 1) may temporarily stop communicationwith the third party system and resume after period of delay (which maybe based on settings). During such a delay, the System 70 (FIG. 1) maystore the data that needs to be pushed to the third party system, and inthe future when the third party system becomes accessible, the necessarysynchronization may take place. Such mechanism enables fault tolerancein the System 70 (FIG. 1) during a situation when the third party systembecomes unavailable and avoids any associated data loss.

It should be noted that there may be no connectivity between the System70 (FIG. 1) and a third party system, and in such a setup,synchronization of appropriate data in both systems may be accomplishedby implementing the System 70 (FIG. 1) to export the appropriate datainto one or more files (in appropriate format) and import those filesinto the other system and vice versa, along with optionally usingworkflow rules in both systems. One having ordinary skill in the artwould appreciate that exporting to one or more files and importing fromone or more files into the System 70 (FIG. 1) may be automated usingRule Action(s) in the Workflow Module.

In an embodiment of the System 70 (FIG. 1), based on implementationpreferences, a workflow rule may be created with a Rule Triggering Eventbased on a pre-scheduled time (for example, Friday 5 pm, every Sunday 6pm, or the like) specified by a user and a Rule Action that (i)generates one or more reports specified by the user, and (ii) sends theone or more reports via one or more communication modes (such as email,text, and the like) to one or more recipients specified by the userand/or publishes to user specified websites including, but not limitedto, a company website, an intranet, a social media website, and thelike. It should be noted that based on implementation preferences, theforegoing functionality may be implemented as a custom feature in theSystem 70 (FIG. 1) without using Workflow Module.

FIG. 22 is a flowchart illustrating actions performed when connectdisposition field is updated, in accordance with an embodiment ofWorkflow Module. As shown by block 782, the system checks whether aconnect disposition is updated. If the connect disposition is updated(in block 782), the system proceeds to check whether the connectdisposition update as a Rule Triggering Event that may act as a triggerfor executing a rule, as shown in block 784. If the update to theconnect disposition act as a Rule Triggering Event (in block 784), thesystem proceeds to perform/execute workflow actions associated with therule that was triggered by the connect disposition update (acting as theRule Triggering Event), as shown by block 786. Based on implementationpreferences, the foregoing Rule Triggering Event may trigger one or morethan one rule, wherein the actions associated with the one or more thanone rule may be executed concurrently or sequentially or a combinationof the two.

FIG. 23 is an exemplary screen view illustrating an interface showing alist of workflow rules configured, in accordance with an embodiment ofWorkflow Module. As shown in FIG. 23, a tabular list 801 shows threeworkflow rules, wherein for each rule/row the Rule Triggering Event andassociated actions associated with the rule are shown under therespective columns. Row 802 shows a workflow rule with “an agent updatesconnect disposition with a value equal to “No longer works there” as aRule Triggering Event definition, and Update “lead status” field as “BadData” as the action. Add New Workflow Rule button 803 may be clicked toadd a new workflow rule.

When a user/talker or a person designated by the user or a businessassociated with the talker (referred to herein as the “Purchaser”) needsto purchase a license to use the System 70 (FIG. 1) for one or moredialing sessions, typically the Purchaser may be required to communicatewith a representative of the Vendor (the term Vendor is defined in theU.S. patent application Ser. No. 14/204,505) via phone or email topurchase the license. Such a process to purchase the license may be timeconsuming, cumbersome, take significant time for the Purchaser topurchase, and add cost overhead to the Vendor which in turn maydiscourage the Vendor from selling dialing sessions of smallerquantity/volume. Further, it should be noted that after purchasing alicense there may be significant delay to provide access to the system,which in turn may not enable the user to get started right away. Hence,there is a need for a module or system providing electronic commercefunctionality that enables a Purchaser to purchase, a Vendor to selllicense for one or more dialing sessions, and the Purchaser (or anotherauthorized user) to start using the system without delay. Suchelectronic commerce functionality is referred to herein as the“Ecommerce Functionality.” Ecommerce Functionality may allow a Vendor tosell dialing sessions of varying volume, and dialing sessions havingvarious characteristics (described below); and thereby providingflexibility in business model choices for the Vendor.

It should be noted that in an embodiment of the System 70 (FIG. 1)utilizing phone call based and non-phone call based communication modes,the Purchaser may be able to purchase licenses for products utilizingphone call based and non-phone call based communication modes. Forexemplary purposes, one or more embodiments of the System 70 (FIG. 1)utilizing phone call based communication modes and having EcommerceModule, are provided below.

A dialing session may have one or more characteristics that include, butare not limited to, (a) duration of the dialing session, (b) minimumnumber of dialing agents that need to be actively engaged tomake/navigate calls concurrently, (c) maximum number of dialing agentsthat may be engaged to make/navigate calls concurrently, (d) minimumnumber of dials that need to be made/navigated by the dialing agentswithin the specified session duration, (e) minimum number of live callsconnected with customers that are transferred to one or more talkers,(f) characteristics of the dialing agents that are allowed to provideservices for the dialing session, (g) geographical location from wherethe dialing agents are from and/or living, (h) type and configuration ofsystem resources (including but not limited to type and configuration ofcommunication links, type and configuration of computers, whethermulti-tenant or dedicated, or the like) to be utilized for the dialingsession, or (i) the like.

It should be noted that the dialing agent characteristics may includebut are not limited to, technical skills, aptitude, linguistics, or thelike. Further, it should be noted that the geographical region where thedialing agents are from and/or living may be of significance becausetheir regional accent and communication skills may be different based onthe geographical location. Based on implementation preferences, eachdialing session may or may not have additional criteria such as whethera purchased dialing session may be split into more than one dialingsessions, criteria to have each dialing session of specific minimumduration, criteria to start a dialing session at the top of the hour ormiddle of the hour, criteria such as a dialing session may not bescheduled during specific time period and once scheduled the dialingsession may be cancelled only by providing specific cancellation noticeor may not be cancelled, or the like. One having ordinary skill in theart would appreciate that a dialing session may have many othercharacteristics not explicitly described herein and all suchcharacteristics are included in the Ecommerce Functionality describedherein. One having ordinary skill in the art would understand thatEcommerce Functionality may enable the Vendor to sell dialing sessionshaving various combinations of characteristics, which otherwise may notbe commercially feasible without Ecommerce Module due to various factorsincluding, but not limited to, time and cost involved in configuringdialing sessions having various such combination of characteristics andselling to Purchaser via traditional methods.

For purposes of selling and purchasing with ease, a license for eachdialing session with certain characteristics may be designated as aproduct (referred to herein as the “Product”). For example, a licensefor a dialing session of 1 hour duration having dialing agents thatspeak and understand English who are from the United States may bepackaged as Product 1, a license for a dialing session to make 200 dialshaving dialing agents that speak and understand French who are fromFrance may be packaged as Product 2, a license for a dialing session toprovide 8 live calls connected with the customers and transferred to oneor more talkers and having dialing agents that speak and understandSpanish who are from Spain may be packaged as Product 3, and the like. Aperson having ordinary skill in the art would appreciate that there maybe many different Products created having different characteristics andthe price for each such Product may vary accordingly. In accordance withthe Ecommerce Functionality, a Vendor may pre-configure several Productsand make it available as pre-configured Product templates for ease ofselecting and purchasing by the Purchaser. Further, a Purchaser may beallowed to customize a pre-configured Product template or configure anew Product by selecting the necessary characteristics and save eachsuch custom configuration as a new Product template in the System 70(FIG. 1), wherein such new Product template may be used during thefuture purchase(s).

An exemplary embodiment of the Ecommerce Functionality implemented as amodule in System 70 (FIG. 1) is referred to herein as the “EcommerceModule.” The Ecommerce Module may require the Purchaser to provideinformation about the Purchaser's identity, such as first name, lastname, business name, title, phone number, email address, or the like.Further, an option may be provided to the Purchaser to allow theEcommerce Module to create a login with a user name and password whichmay be used for a future login in the Ecommerce Module. Further, afterselecting one or more Products with associated quantities, the EcommerceModule may provide option for the Purchaser to make payments in variousmodes, including but not limited to, online payment through credit card,online payment through debit card, electronic fund transfer, paymentthrough check, payment through third party systems, electronic money ordigital currency, or the like, or any combination thereof. It should benoted that a payment amount may be split and paid through one or morepayments through one or more payment modes. Further, a Purchaser of theSystem 70 (FIG. 1) may be forced to review and electronicallyacknowledge license terms and conditions during the purchase of licensefor one or more dialing sessions in the Ecommerce Module, or as part ofthe process creating the login in the Ecommerce Module, or beforestarting a dialing session, or the like. In an embodiment of theEcommerce Module, based on implementation preferences, the system mayrecommend one or more products based on the business solution thePurchaser is looking for, and facilitate the purchasing process.

Further, during the purchase process, a Purchaser may be allowed toenter one or more promotion/coupon codes and the price associated with aProduct may be adjusted accordingly. The Ecommerce Module mayautomatically apply one or more promotion codes and adjust the priceassociated with one or more Products selected for purchase, based on:(a) the referring website from where the Purchaser came to a websiteoffering Ecommerce Functionality, (b) historical data associated withthe Purchaser's visits to the website, which may be tracked usingcookie(s) stored in the Purchaser's computer device(s). Based onimplementation preferences, the foregoing price adjustment may beapplied with or without the knowledge of the Purchaser. One havingordinary skill in the art would appreciate that the foregoingfunctionality related to electronically tracking a profile of aPurchaser, history of the Purchaser's visits to a website offeringEcommerce Functionality, metrics associated with navigation pattern ofthe Purchaser within the website offering Ecommerce Functionality(including, but not limited to, time spent on each link and repeatedvisits to certain links), and the like, may be implemented by developinga module with such functionality or by integrating with a PriorMarketing Automation System or Enhanced Marketing Automation System(defined in the U.S. patent application Ser. No. 14/204,505) thatprovides tracking functionality for marketing purposes.

Upon a Purchaser purchasing a license for one or more dialing sessions,the Ecommerce Module may automatically update the appropriateinformation (related to the purchase) to a Scheduling App (defined inthe U.S. patent application Ser. No. 14/204,505), wherein the SchedulingApp may be implemented as a module as in the System 70 (FIG. 1) or as aseparate system outside of the System 70 (FIG. 1). It should be notedthat the Scheduling App may keep track of the number of dialing sessions(with associated characteristics) purchased, how much has been used, howmuch is remaining to be used in the future, and the like.

A person with ordinary skill in the art would appreciate that the System70 (FIG. 1) may provide access to a dialing session reasonably quicklyfrom the time the Purchaser is ready to start the dialing session soonafter purchasing a license, by having the Ecommerce Module andScheduling App implemented as envisioned by the invention describedherein, wherein the Purchaser may purchase a dialing session usingEcommerce Module, schedule the dialing session, start the dialingsession, and the like in a reasonably short period of time (for example,within few minutes). Based on implementation preferences, scheduling adialing session (or other communication session via phone call ornon-phone call based communication mode) may be optional, wherein aPurchaser may use the communication session based on on-demandmodel/walk in without pre-scheduling. It should be noted that a licensepurchased through the Ecommerce Module may involve, but is not limitedto, a dialing session that includes human dialing agents, a dialingsession wherein the function of one or more dialing agents areautomated, a texting session that comprises human texting agents, atexting session wherein the function of one or more texting agents areautomated, a voice message drop Service Request, sending an emailService Request, and the like. One of ordinary skill in the art wouldappreciate that other forms of customization of Product that are notdisclosed herein that are familiar to those of ordinary skill in the artmay be offered by a system embodying Ecommerce Functionality.

FIG. 24 is a flowchart illustrating actions performed by a Purchaserduring a purchase, in accordance with an embodiment of the EcommerceFunctionality. As shown by block 822, a Purchaser visits a website tobuy a Product. As shown by block 824, the Purchaser customizes theProduct to purchase. As shown by block 826, the Purchaser provides thePurchaser's identification and other credentials relevant for thepurchase. As shown by block 828, the Purchaser completes the purchase.As shown by block 830, the Purchaser (or another authorized user) mayschedule and start a communication session based on the purchasedProduct. Based on implementation preferences, the foregoing step asshown by block 830 may be optional and it may not immediately follow thestep as shown by block 828. Further, scheduling a communication session(as shown by block 830) may be optional (that is, based onimplementation preferences, the Purchaser or another authorized user maystart a communication session without scheduling the communicationsession).

FIG. 25 is an exemplary screen view illustrating an interface showing afirst step when a Purchaser purchases a Product, in accordance with anembodiment of the Ecommerce Functionality. As shown in FIG. 25, aPurchaser may select a Product in drop down list control 842, and uponselecting the Product, the section below the Product may showappropriate controls (which may be based on the selected Product) thatallows the Purchaser to further specify/customize the attributesassociated with the selected Product. Upon selecting Phone Call Sessionas the Product, radio button 844 may be selected/enabled by thePurchaser to specify that the selected Product Phone Call Sessioninvolves one or more dialing agents. Further, under the section“Customize the selected Product” there may be one or more checkboxes 846that allows the Purchaser to customize the selected Product further.Text box 848 allows the Purchaser to specify the number of users thatmay be using the Product. The Purchaser may click “Proceed to Next Step”button at the bottom of the interface to go to the next step in thepurchasing process as shown in FIG. 26.

FIG. 26 is an exemplary screen view illustrating an interface showing asecond step when a Purchaser purchases a Product, in accordance with anembodiment of the Ecommerce Functionality. As shown in FIG. 26, section862 shows controls that allow the Purchaser to input the values for thefields associated with Purchaser's identification. Price field 864 showsthe price for the Product that was selected/customized during the firststep of the purchasing process as shown in FIG. 26, wherein the priceshown in 862 may be calculated by the system automatically. Section 866shows the controls for the Purchaser to input the payment method andcredit card information. At the bottom of the interface, the Purchasermay click the “Complete Purchase & Close” button to complete thepurchasing process and close the screen, or the Purchaser may click the“Complete Purchase & Proceed to schedule/Use the Product” button tocomplete the purchasing process and proceed to schedule and/or use theProduct that was purchased (which may take the Purchaser to the nextstep in the purchasing process as shown in FIG. 27).

FIG. 27 is an exemplary screen view illustrating an interface showing athird step when a Purchaser purchases a Product, in accordance with anembodiment of the Ecommerce Functionality. As shown in FIG. 27, thePurchaser or a user of the system, Text field 882 allows entering theuser name of the person for whom the usage of the purchased Product isscheduled. Control 884 enables selecting date and time for using theproduct by the user identified in 882. Drop down list 886 allowsspecifying the usage duration when the Product is used at the scheduleddate and time specified in 884. At the bottom of the interface, uponclicking the “Confirm Schedule & Start Communication Session” button,the specified schedule is confirmed and the system may begin theCommunication Session.

One having ordinary skill in the art would appreciate that the System 70(FIG. 1) may have one or more users (such as talkers, dialing agents,texting reps, texting agents, Call Handlers, Third Party CallParticipants, and/or other users) concurrently performing a roleassociated with each such user. The behavior of each such user in theSystem 70 (FIG. 1), may affect the outcome of using the System 70 (FIG.1). That is, if the behavior of a user meets certain requiredstandards/best practices associated with the role of the user, theoutcome of using the System 70 (FIG. 1) may meet the expectation.However, if the behavior of the user does not meet the requiredstandards/best practices associated with the role of the user, theoutcome may not be favorable and fall short of the expectation. Theforegoing reason may necessitate tracking of the behavior of a user andtaking corrective action. If such tracking and taking corrective actionis performed manually it may be time consuming and cumbersome, and henceit is desirable to have a module in the System 70 (FIG. 1) thatautomates the tracking of the behavior of a user and taking correctiveaction if necessary. Such module is referred to herein as the “BehaviorTracking and Learning Management System” or “BTLMS” or “BTLMS module.”

One having ordinary skill in the art would appreciate that there may bedifferent behavioral actions associated with each role played by a userin the System 70 (FIG. 1). For example, the behavior of a userperforming the role of a talker may include, but is not limited to,selecting/uploading one or more customer lists for dialing, scheduling adialing session, conducting the dialing session, reviewing notes historyof the customers that are being dialed or scheduled to be dialed next,attending and talking to a customer in a transferred call in a timelymanner, wrapping up the call and entering notes in a timely manner afterthe call ends with the customer, taking a break from dialing for onlyspecified amount of time, taking training courses periodically, or thelike. As a way of another example, behavior of a user performing therole of a dialing agent may include, but is not limited to, logging inand making the dialing agent available, navigating a phone call promptlyby engaging phone trees or operators and getting past them, quicklyrecognizing when a customer answers a call and transferring the call ina timely manner to a talker, taking a break from dialing for onlyspecified amount of time, taking training courses periodically, or thelike.

An embodiment of the BTLMS module may learn the behavior of a user inthe System 70 (FIG. 1) and upon the user behavior matching a pre-definedpattern (such pattern is referred to herein as the “Pre-definedPattern”) of behavior associated with not meeting performance standardsfor the role played by the user, the BTLMS module may recognize that theuser is deviating from the required performance standards/best practicesassociated with the role of the user, and may recommend or force theuser to take one or more training courses. It should be noted that basedon implementation preferences, the Pre-defined Pattern may involvebehavior for a specific role associated with meeting performancestandards and in which case, the BTLMS module may expect behavior of allusers (associated with the role) to match with the Pre-defined Patternand if there is not a match it will be recognized as a deviation. Onehaving ordinary skill in the art would appreciate that there may be avariety of ways to implement a Pre-defined Pattern and to recognize auser behavior deviating from the expected behavior, based on which theBTLMS module may recommend or force the user to take one or moretraining courses.

It should be noted that the Pre-defined Pattern may have one or moreactions (associated with the user behavior), and the one or more actionsmay or may not be in a specific order. Further, to deem that a userbehavior matches a Pre-defined Pattern, there may be numerouscombinations that may be defined and determined. For example, to deemthat a user behavior matches a Pre-defined Pattern, any one or moreactions of the user behavior may need to match with any one or moreactions associated with the Pre-defined Pattern, or all of the actionsof the user behavior may need to match with all of the actionsassociated with the Pre-defined Pattern, or the like. It should be notedthat an action associated with a Pre-defined Pattern for a role of auser may require the user to take a particular training course once inspecific time duration. For example, an action associated with aPre-defined Pattern for the role of a talker may require the talker totake a training course that teaches the talker about the features of theSystem 70 (FIG. 1) that are relevant to the role of the talker and howto use them effectively, once in 6 months.

As a first example of a Pre-defined Pattern for the role of a talker, apattern of behavior that defines the behavior of a talker deviating fromthe required best practice is defined as follows: a talker responding toa transferred call with a delay of more than one-fourth of a second andsuch delayed response takes place for more than 5% of the transferredcalls during a period of one month. Upon the behavior of a talkermatching the Pre-defined Pattern provided in the foregoing firstexample, the talker may be recommended or forced to take a course thatteaches the importance of: responding without delay when a call istransferred to the talker, ramifications of not addressing the delay,benefits of addressing the delay, and the like. As a second example of aPre-defined Pattern for the role of a talker, a pattern that involves: atalker taking more than five minutes of time to enter notes/wrap up acall after the transferred call is ended with the customer. Upon thebehavior of a talker matching the Pre-defined Pattern provided in theforegoing second example, the talker may be recommended to take a coursethat teaches the importance of wrapping up the transferred call andentering notes within a specified amount of time after the transferredcall is ended, ramifications of not wrapping up the call in a reasonableamount of time, benefits of wrapping up the call in a reasonable amountof time, and the like. As a third example of a Pre-defined Pattern forthe role of a dialing agent, a pattern that involves a dialing agentrecognize a live customer answering a call and initiating the transferof the call with a delay of more than one-fourth of a second and suchdelayed transfer take place for more than 2% of the transferred callsduring a period of a week. Upon the behavior of a dialing agent matchingthe Pre-defined Pattern provided in the foregoing third example, thedialing agent may be recommended to take a course that teaches theimportance of transferring a call without delay, ramifications of notaddressing the delay, benefits of addressing the delay, and the like.One having ordinary skill would appreciate that there may be numerouscombinations of behavioral actions to define many Pre-defined Pattersand all those Pre-defined Patterns are anticipated by the presentinvention associated with BTLMS.

Taking a course may include, but is not limited to, a usertaking/learning and completing a course electronically using a computerof the user at a pace of the user or at the pace defined in the courseor associated with the course, taking an instructor-led courseelectronically using the computer of the user, or taking a class roombased instructor-led course by attending a class room training, or thelike. Further, taking a course may include additional criteriaincluding, but not limited to, a requirement to answer one or morequestions or take one more tests associated with the course and achievea passing score.

Further, based on implementation preferences of BTLMS, alerts (email ortext or in other forms) may be generated by the system to providereminder to individual(s) that are recommended or forced to take one ormore training courses. Also, at specific times or time intervals, thesystem may automatically generate/send status report(s) to specificrecipients (with appropriate information that is of interest to therecipients) or allow authorized personnel to manually generate suchreport.

A conventional learning management system (referred to herein as the“LMS”) that exists presently may provide functionality including, but isnot limited to, allowing one or more users to learn by accessing contentdisseminated via the LMS, allowing one or more users to author thecontent, allowing one or more users to review/approve the content,enrollment of different types of users, tracking user activity withinthe LMS (such as which user took what course, whether the course was yetto be completed, if the course if partially completed where did the userleave off, when was the course completed, what was the score, or thelike), and other functionality customary to LMS. One having ordinaryskill in the art would appreciate that the BTLMS may be able toaccomplish certain features (that are readily provided in a typical LMSsystem) by integrating with a LMS system or implementing those featuresas part of the BTLMS. It should be noted that when comparing to atypical LMS, the BTLMS has distinctive differences in functionalityincluding, but is not limited to, tracking the behavior of a user in theSystem 70 (FIG. 1) and taking corrective action when the behavior ismatching (or not matching, based on implementation preferences) with oneor more Pre-defined Pattern. Hence, the BTLMS improves adherence to bestpractices without increasing time and cost investment, and therebyimproves the chances of favorable outcome of using the system 70 (FIG.1).

FIG. 28 is a flowchart illustrating actions performed to track andmonitor a user behavior, in accordance with an embodiment of BTLMS. Asshown by block 902, the system may track and monitor the behavior of auser against a Pre-defined Pattern (defining one or more unacceptablebehaviors). As shown by block 904, the system checks whether the user'sbehavior matches the Pre-defined Pattern. If the system determines thatthe user's behavior matches the Pre-defined Pattern (in block 904), thesystem may proceed to recommend or force the user to take a trainingcourse (more training courses) for correcting/mitigating theunacceptable behavior associated with the Pre-defined Pattern, as shownby block 906.

FIG. 29 is an exemplary screen view illustrating an interface showing afirst step in defining a Pre-defined Pattern and associated trainingcourse(s), in accordance with an embodiment of BTLMS. As shown in FIG.29, checkbox 922 allows an authorized user to enable the system tosuggest one or more training courses to a user whose behavior matchesthe Pre-defined Pattern (of unacceptable behavior) defined below.Section 924 allows the authorized user to specify one or moreunacceptable behaviors associated with the Pre-defined Pattern. At thebottom of the interface, when the authorized user clicks the “Save andProceed to specify training course(s)” button the system proceeds to thenext interface (as shown in FIG. 30).

FIG. 30 is an exemplary screen view showing a second step in defining aPre-defined Pattern and associated training course(s), in accordancewith an embodiment of BTLMS. As shown in FIG. 30, section 942 shows amessage describing which unacceptable user behavior have been observedby the system, shown to a user upon the user's behavior matching withthe Pre-defined Pattern of unacceptable behavior. It should be notedthat the unacceptable behavior shown in 942 is based on the unacceptablebehavior(s) associated with the Pre-defined Pattern specified in thefirst step (as shown in FIG. 29). Section 944 shows one or more trainingcourses recommended by the system for the user to take (by clicking thelinks associated with the courses) before proceeding to the nextcommunication session (dialing session, in this case). The authorizeduser configuring the BTLMS settings, may select or de-select one or moreof the recommended training courses to be presented when a user's mateswith the Pre-defined Pattern of unacceptable behavior. It should benoted, based on implementation preferences, a training course may be atraining video. For example, section 944 lists 2 training videos (firstone 2.5 minutes in duration and the second one 2 minutes in duration) asthe training courses and the user is recommended to view those videos(which may be considered as taking training courses). At the bottom ofthe interface, when the authorized user clicks the “Save and ConfirmBTLMS Settings” button the system saves and enables the BTLMS settingsfor the Pre-defined Pattern of unacceptable behavior. It should be notedthat in the foregoing exemplary interface shown in FIG. 30 only onePre-defined Pattern may be configured in the system. One having ordinaryskill in the art would appreciate that based on implementationpreferences, the system may allow configuration of more than onePre-defined Pattern.

It will be apparent to those skilled in the art that variousmodifications and variations can be made to the structure of the presentinvention without departing from the scope or spirit of the invention.In view of the foregoing, it is intended that the present inventioncover modifications and variations of this invention provided they fallwithin the scope of the following claims and their equivalents.

What is claimed is:
 1. A system for establishing a communication with acustomer by an agent, via one or more communication modes, comprising:an agent computer comprising a first processor and a first memoryconfigured to store non-transitory instructions that when executed bythe first processor performs the steps of: receiving an identifynotification that enables the agent computer to identify a customer(referred to herein as an identified customer) for the communication;receiving agent schedule information that enables identifying a scheduletimeslot of the agent as predicted by the system for a communicationsession; and a second computer comprising a second processor and asecond memory configured to store non-transitory instructions that whenexecuted by the second processor performs the steps of: providing theidentify notification enabling the agent computer to identify theidentified customer, wherein the system predicts the schedule timeslotof the agent, by taking into account a number of agent based touchesthat may need to be executed.
 2. The system of claim 1, whereinpredicting the schedule timeslot of the agent for the communicationsession further comprises the step of taking into account agentavailability data.
 3. The system of claim 2, wherein the agentavailability data is predicted by the system.
 4. The system of claim 2,wherein the agent availability data includes agent availability dataprovided by the agent and/or agent availability data available from athird party system.
 5. The system of claim 1, wherein the number ofagent based touches, during various time periods, is predicted by thesystem.
 6. The system of claim 1, wherein predicting the scheduletimeslot of the agent for the communication session further comprisesthe step of by taking into account one or more of the data from thegroup consisting of agent availability for the execution of agent basedtouches, agent availability data associated with other agents, marketingoutcome correlation data, and the number of agent based touches that mayneed to be executed at various timeslots.
 7. The system of claim 1,wherein the agent computer is configured to graphically show thepredicted schedule timeslot of the agent for the communication sessionversus the actual agent availability for the timeslot.
 8. The system ofclaim 1, wherein one or more agent based touches are associated with amulti-touch marketing campaign.
 9. The system of claim 1, wherein ifagent availability is not sufficient to execute a future agent basedtouch during an execution time associated with the agent based touch,the system proactively updates or replaces the agent based touch with anon agent based touch or changes the order of the touches by switchingthe agent based touch with a non agent based touch.
 10. The system ofclaim 1, wherein the predicted schedule timeslot of the agent isscheduled to have the agent participate in a communication session,wherein agent based touches are performed during the communicationsession.
 11. The system of claim 1, wherein the one or morecommunication modes include one or more of the group consisting of aphone call, a voice message, a communication using automated phonetechnology, an email, a text message, a chat, an instant message, avideo, a short message service (SMS) message, and a multimedia messagingservice (MMS) message.
 12. The system of claim 1, wherein the agentcomputer is further configured to receive a batch notification thatenables the agent computer to identify a batch of one or more customerrecords in the agent computer for communication, wherein at least onecustomer record of the identified customer is part of the batch.
 13. Thesystem of claim 1, further comprising a third computer comprising athird processor and a third memory configured to store non-transitoryinstructions that when executed by the third processor performs the stepof: providing a transferred notification acknowledging that a customerthat has been attempted for communication has been transferred, referredherein as a transferred customer, wherein at least one customer recordof the transferred customer is part of a customer record of theidentified customer.
 14. The system of claim 1, wherein the systemfurther comprises a communication assistance module for providing atransferred notification confirming that a customer that has beenattempted for communication has been transferred, referred herein as atransferred customer, wherein at least one customer record of thetransferred customer is part of a customer record of the identifiedcustomer, and wherein the communication assistance module partially orfully automates communication attempt with the transferred customer andthe interaction with the transferred customer up until prior to thetransfer.
 15. The system of claim 11, wherein the communication usingautomated phone technology consists of an interactive voice response(IVR) system.
 16. A method for using an computer controlledcommunication system comprising a processor and a memory forestablishing a communication with a customer by an agent, via one ormore communication modes, comprising the steps of: receiving an identifynotification that enables identifying a customer (referred to herein asan identified customer) for the communication; receiving agent scheduleinformation that enables identifying a schedule timeslot of the agent aspredicted by the method for a communication session; and predicting theschedule timeslot of the agent by taking into account a number of agentbased touches that may need to be executed.
 17. The method of claim 16,wherein predicting the schedule timeslot of the agent for communicationsession further comprises the step of taking into account agentavailability data.
 18. The method of claim 17, further comprising thestep of predicting the agent availability data.
 19. The method of claim17, wherein the agent availability data includes agent availability dataprovided by the agent and/or agent availability data available from athird party system.
 20. The method of claim 16, further comprising thestep of predicting the number of agent based touches, during varioustime periods.
 21. The method of claim 16, wherein predicting theschedule timeslot of the agent for the communication session furthercomprises the step of taking into account one or more of the data fromthe group consisting of agent availability for the execution of agentbased touches, agent availability data associated with other agents,marketing outcome correlation data, and the number of agent basedtouches that may need to be executed at various timeslots.
 22. Themethod of claim 16, further comprising the step graphically showing thepredicted schedule timeslot of the agent for the communication sessionversus the actual agent availability for the timeslot.
 23. The method ofclaim 16, wherein one or more agent based touches are associated with amulti-touch marketing campaign.
 24. The method of claim 16, furthercomprising the step of if agent availability is not sufficient toexecute a future agent based touch during an execution time associatedwith the agent based touch, the agent based touch is proactively updatedor replaced with a non agent based touch or the order of the touches arechanged by switching the agent based touch with a non agent based touch.25. The method of claim 16, wherein the predicted schedule timeslot ofthe agent is scheduled to have the agent participate in a communicationsession, and agent based touches are performed during the communicationsession.
 26. The method of claim 16, wherein the one or morecommunication modes include one or more of the group consisting of aphone call, a voice message, a communication using automated phonetechnology, an email, a text message, a chat, an instant message, avideo, a short message service (SMS) message, and a multimedia messagingservice (MMS) message.
 27. The method of claim 16, further comprisingthe step of receiving a batch notification that enables identifying abatch of one or more customer records for communication, wherein atleast one customer record of the identified customer is part of thebatch.
 28. The method of claim 16, further comprising the step of:providing a transferred notification acknowledging that a customer thathas been attempted for communication has been transferred, referredherein as a transferred customer, wherein at least one customer recordof the transferred customer is part of a customer record of theidentified customer.
 29. The method of claim 16, further comprising thesteps of: providing a transferred notification confirming that acustomer that has been attempted for communication has been transferred,referred herein as a transferred customer, wherein at least one customerrecord of the transferred customer is part of a customer record of theidentified customer; and partially or fully automating a communicationattempt with the transferred customer and the interaction with thetransferred customer up until prior to the transfer.
 30. The method ofclaim 26, wherein the communication using automated phone technologyconsists of an interactive voice response (IVR) system.